Re: ERXMigrationTable.newColumn does not set default value
Re: ERXMigrationTable.newColumn does not set default value
- Subject: Re: ERXMigrationTable.newColumn does not set default value
- From: Mike Schrag <email@hidden>
- Date: Thu, 10 Apr 2008 08:50:53 -0400
I lied anyway ... I DID actually add it to PGSQL, but I was looking in
the same wrong place that you were. FB PlugIn has two inner classes
(the schemasync and the expression). That method is actually in
expression, not in sync, so when I looked in PG, I didn't see it.
However, it IS in PGExpession. So I suspect your problems with
defaults not working are due to 5.4. I'll have to check this for the
next WO version, but I SUSPECT it works properly ...
ms
On Apr 10, 2008, at 8:38 AM, Mike Schrag wrote:
The statment is built by a call of
EOSchemaSynchronizationFactory._columnCreationClauseForAttribute
method which calls - in my case
I take it (based on the class name you're referencing here) that
you're using WO 5.4.x? The problems I've discussed previously with
respect to SQL generation in 5.4.x make this not worth trying to fix
on your 5.4.x build until the next WO release ...
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden