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: Tue, 22 Apr 2008 13:23:54 -0400
Okay, I'll get the ability to read the
"er.extensions.eoattribute.default" along with the simpler "Default"
from the userInfo dictionary setup in the ERXMicrosoftPlugIn like it
is in the FrontbasePlugIn, and then hand it off you you and Chuck
for review.
"Default" is a contrivance added in the FB plugin only, and is not
used by anything, so I wouldn't bother. I actually would have used
"Default" except that FB decided to define that thing as having an
unclear attribute formatting, which I why I defined a new one.
Out of curiosity, what does the defaultValue parameter as defined in
the Wonder API for ERXMigrationsTable.newXxxxColumn() do?
For example: http://webobjects.mdimension.com/wonder/api/er/extensions/migration/ERXMigrationTable.html#newStringColumn(java.lang.String, int, boolean, java.lang.String)
It gets passed as a default value for the database column (you can see
the sql it generates). This exists only to accommodate migrations
from allows null true to allows null false to deal with existing data
and should not be relied on for ANYTHING else.
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