Hi Henrique, maybe it's all easier with small databases, and small teams, yes.
Am 09.10.2012 um 12:44 schrieb Henrique Gomes <[email protected]>: > IMHO, I think you are over complicating for no obvious gain. If two features > are developed in parallel, either reconcile them before release / production > or, if they are released separated, just rename the latter migration before > release. You are using development databases for each developer, and > periodically reseting them, right? Yes, but only on weekends usually, because resetting a 40 GB database takes some time, multiplied by 3 developer databases, a staging system and an integration system. Jenkins builds automatically and I don't want tests to fail there just because someone checked in something in the wrong order. > I have the exact situation that i'm developing two different features on two > different branches of code. The migrations on each branch are named the same > because I do not know which one I'll release first. Then I'll rename the > other. The only pain, that last 5 seconds, is reseting the database when I > change branch. That's a simple "gzip -dc db.dump.gz | psql dbname" I don't have the time during the day to wait for a re-import of the whole database like this. And yes, I need the entire database to develop, because otherwise I'm unable to reproduce issues occurring in production. 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/archive%40mail-archive.com This email sent to [email protected]
