Hi,
Since Chuck said "Use prototype, or you're stupid" in his awesome
session in WOWODC 08, I looked into my project and realized that I
need to modernize it: legacy format (eogenerator / Xcode project / not
fluffy bunny layout), not using prototype in EOModel, using
session().defaultEditingContext(), pageWithName("ClassName"), etc.
Thanks to the help from David LeBer and Pascal, I converted my project
into fluffy bunny during WWDC webobjects lab.
However, when I come back and try to continuely improving my code, I
got a little bit confused about migration.
Today I read an article about migration:
http://www.stepwise.com/Articles/2005/DBChanges/index.html
finally I realized where all the java file in my project like
Database.java, Updater.java, Update0.java come from. Of course I
didn't write the corresponding UpdateX.java file since I have no idea
what it do before. When I changed EOModel, I just manually write SQL
statement and paste into psql.
Now we have er.extensions.migration. How do I convert those old-school
java file into WONDER world? I mean, my app has already run as
production server for a long time. How do I leverage the ERXMigration
into a project that didn't start with ERXMigration at first? After
that, when I make changes to EOModel, I must create an migration class
like MyMigrationX+1 right? Anything else?
And I'm adding prototype to my EOModel, which changes my EOModel a
lot. (each attribute will be assigned a prototype, which my change
their type or width.) Should I write my migration class for every
column manually? Is there any way to generate those migration
automatically?
Regards,
yllan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
