Re: ERXMigrationDatabase and postUpgrade
Re: ERXMigrationDatabase and postUpgrade
- Subject: Re: ERXMigrationDatabase and postUpgrade
- From: Ramsey Lee Gurley <email@hidden>
- Date: Sat, 11 Apr 2009 08:57:36 -0400
On Apr 11, 2009, at 1:18 AM, Sanford Selznick wrote:
At 2:22 PM -0700 4/10/09, Mike Schrag wrote:
PS - Wouldn't it be cool if the migration generator in Entity
Modeler would use the string constants from the model for table
and column names instead of in-line strings? :-)
it can't for two reasons --
one is that your model will change over time and the constant you
refer to in migration0 might not exist in a month, so it would stop
compiling.
I _want_ the compiler error. I'd much rather get a compiler error
than a runtime error.
Test suites are of course important. But the more errors I can get
on the compile time side of the fence, the better.
Unfortunately, you would never be able to remove a column. Ever.
Migrations generation would not be very useful then.
I'd rather see some sort of Resources/Model.eomig file to point to the
com.whatever.migration package. If the Migration generator could
compare existing migration state to the current model, then maybe it
could generate Migration1, Migration2, ... MigrationN. That would be
totally awesome.
Ramsey
_______________________________________________
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