The problem is that even though I use:
table.newStringColumn("Some_Column", 255, false, "Default")
The SQL generated is be: ALTER TABLE dbo.My_Table ADD Some_Column
varchar(255) NOT NULL
Which generates an error stating that either it has to be NULL, or a
default be passed. As you can see, I did define a default value
("Default") in the Migration, but the plugin isn't picking it up. I'm
working on getting the ERXMicrosoftPlugIn to do it, but I can't even
find the code in the FrontbasePlugIn that would add the DEFAULT clause
so I'm not sure how to get the Microsoft plugin to do it. That is what
is confusing me.
Dave
On Apr 22, 2008, at 2:46 PM, Mike Schrag wrote:
Even with no rows in the table? That's an odd restriction ...
However, "after table creation" presumably means "in another
migration" which couldn't guarantee the table is empty anyway, so
this seems like a reasonable restriction (as your migration should
probably ALWAYS declare a default for new not-null columns to
protect against this).
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
