At 7:50 AM -0700 4/11/09, Mike Schrag wrote:
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.
No you don't
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.
No you don't :)
Well, not for this at least ... the poi
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
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
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
At 4:49 PM -0400 4/10/09, David Avendasora wrote:
Hi Sanford,
Your Migration class needs to implement IERXPostMigration in order
for that method to get called, I believe.
According to the Package Description for Migrations:
http://webobjects.mdimension.com/wonder/api/index.html?overview-summa
Hi Sanford,
Your Migration class needs to implement IERXPostMigration in order for
that method to get called, I believe.
According to the Package Description for Migrations:
http://webobjects.mdimension.com/wonder/api/index.html?overview-summary.html
To perform a "post op", your migration c
Hello,
I'm experimenting with Migrations. I'm a little new to all this.
What's the proper way to implement postUpgrade? Below is a snippet
of what I've got, but postUpgrade is never called. I don't see an
ERXMigrationDatabase.PostMigration class. And I don't really want to
duplicate w
