• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: ERXMigrationDatabase and postUpgrade
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ERXMigrationDatabase and postUpgrade


  • Subject: Re: ERXMigrationDatabase and postUpgrade
  • From: Mike Schrag <email@hidden>
  • Date: Fri, 10 Apr 2009 14:22:48 -0700

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. 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

ms

_______________________________________________
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


  • Follow-Ups:
    • Re: ERXMigrationDatabase and postUpgrade
      • From: Sanford Selznick <email@hidden>
References: 
 >ERXMigrationDatabase and postUpgrade (From: Sanford Selznick <email@hidden>)
 >Re: ERXMigrationDatabase and postUpgrade (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: [OT] local persistence ORM
  • Next by Date: Re: ERXMigrationDatabase and postUpgrade
  • Previous by thread: Re: ERXMigrationDatabase and postUpgrade
  • Next by thread: Re: ERXMigrationDatabase and postUpgrade
  • Index(es):
    • Date
    • Thread