Le 2012-09-20 à 16:42, David Holt <[email protected]> a écrit :
> Also, can you use dependencies to mitigate the risk of doing something > incorrectly? > > Can you always do migrations in trunk regardless of where the necessity for > them is being created? The problem is that if the migration is adding a non-null column, and the model don't have the attribute, the INSERT or UPDATE will fail. If you had it to the model, you need to add a value to that new column. > > On 2012-09-20, at 1:32 PM, Maik Musall wrote: > >> >> Am 20.09.2012 um 21:22 schrieb Pascal Robert <[email protected]>: >> >>> Hi guys, >>> >>> I was wondering how do you deal with situations where your development >>> branch is having migrations that are NOT part of trunk/current release but >>> that you need to do a migration for a fix in trunk? >>> >>> Let's say trunk is at migration 2 (on the prod database), but the "super >>> new features" branch is at migration 5 (on the dev database), creating a >>> migration 3 in trunk will create problems when trunk is merged with the >>> "super new features" branch, and doing a migration 6 in trunk will make >>> that migration 3-4-5 won't be executed in prod since prod will already be >>> at version 6. >> >> My experiences with migrations are very limited so far, but how about making >> it a habit to do migrations as a separate commit, so you could cherry-pick >> migration 3 separately into trunk? >> >> Maik >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com >> >> This email sent to [email protected] > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
