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: Fri, 11 Apr 2008 15:19:18 -0400
Actually it is. The integrated FB plug-in in WO 5.4.x has the same
capabilities as the Wonder one. May be we should define an extension
to the EOModel format so that we could extent it to all vendors.
I'm not sure about 5.4's implementation, but Wonder has a alternate
default value implementation (to maintain backwards compatibility with
people who expect the standard FB default behavior). The problem is
that the default value as implemented in the FrontBase plugin normally
does not pass the default value through the attribute formatter, so if
you default value is something other than a String (like a default
NSTimestamp), the default value fails. We may be able to just fix the
default value interpretation, though, since I actually believe the
original is wrong ... I just didn't want to risk breaking someone, so
I added an "er.extensions.default" or something like that.
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