Re: Migrations in Production?
Re: Migrations in Production?
- Subject: Re: Migrations in Production?
- From: Jon Nolan <email@hidden>
- Date: Tue, 13 Jul 2010 10:27:05 -0600
- Organization: Loch Garman
My admins won't give the app user create/alter/drop/etc. permissions so
I can't use migrations in prod. However, I do something like Mike
suggests. I'm using the <ModelName>0_Oracle_Upgrade.migration approach
since I could never get Java to handle CLOBs correctly not to mention
the 32 character limit on the foreign keys. I simply test in dev and
stage. Once I know all is well I give the migration script to the
admins with, of course, a little extra to take care of the
dbupdater.version increment. That way I don't have to strip out the
migrations between stage and prod.
Makes them happy and works for me.
On 7/13/10 10:11 AM, Mike Schrag wrote:
Test in a staging environment (that is a production clone) first ... I always used them, though. I've considered making a variant of migrations that just spit out the computed migration SQL instead of applying them directly for environments where you don't want to run them automagically.
On Jul 13, 2010, at 12:08 PM, Farrukh Ijaz wrote:
Hi,
Is anyone using Migrations in production environment? If yes, what is your experience? I was planning to use it but a bit affraid as db changes on the fly frightens me especially in production :)
Farrukh
Sent from my iPad
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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