• 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: AW: EOModeler Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: EOModeler Question


  • Subject: Re: AW: EOModeler Question
  • From: "Jerry W. Walker" <email@hidden>
  • Date: Tue, 26 Jul 2005 17:14:17 -0400

Hi, Anjo,

On Jul 25, 2005, at 5:31 AM, Anjo Krank wrote:

I knew the Article but frankly, I wouldn't feel comfortable to have this an automatic process.

That's interesting. After using this approach for a while on our Intent product, we found that we were less comfortable when this process was NOT automatic. Integrating the SQL into the update classes was not trivial, but neither was it rocket science.


The big advantage, of course, is that when you're ready to test a new build of your app, it checks to see that the DB is at the same version level automatically, and, if the DB is out of date, it brings it up to the appropriate level. You don't even have to be particularly aware that you were out of sync.

With multiple developers developing against the same product, this proved more reliable than trying to hand distribute the latest DB update scripts.

If you found that the DB version got ahead of you because you took overly long to check your changes into the repository, a simple CVS update, a rebuild of the app and a test run would put your code and the DB back in sync.

If you happened to have a local version of the test DB running on your workstation, no problem, it was automatically brought up to date as well by a CVS update, a rebuild and a test run.

Regards,
Jerry

Cheers, Anjo

Am 25.07.2005 um 10:44 schrieb Helge Staedtler:


For changes also beeing reflected in your deployment-DB after you have done
all the testing in development, the following stuff might come in handy...


http://wocode.com/cgi-bin/WebObjects/WOCode.woa/1/wa/ShareCodeItem? itemId=42
4


Just collect all of your SQL-statements and put them in this stuff, to
distribute the changes in the database to ALL live-systems on deployment.


But read the corresponding article carefully before starting with this...
...you need to know what you are doing. ;-)




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40codefab.com


This email sent to email@hidden



--
__ Jerry W. Walker, Partner
C o d e F a b, LLC - "High Performance Industrial Strength Internet Enabled Systems"
email@hidden
212 465 8484 X-102 office
212 465 9178 fax



_______________________________________________ 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
References: 
 >AW: EOModeler Question (From: Helge Staedtler <email@hidden>)
 >Re: AW: EOModeler Question (From: Anjo Krank <email@hidden>)

  • Prev by Date: Re: many-to-many with attributes?
  • Next by Date: Re: many-to-many with attributes?
  • Previous by thread: Re: AW: EOModeler Question
  • Next by thread: Re: EOModeler Question
  • Index(es):
    • Date
    • Thread