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.
also the value in the migration is the external name for the
attribute (the column name) not the attribute name, and the eogen
constants are attribute names
Then we need more constants! :-)
All the best,
Sanford
_______________________________________________
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]
