Modifying migrations when refactoring models

[rdsoze]

I think creating a new migration is better than modifying existing migrations which currently happens when refactoring models.

[jcrisp]

certainly once your schema is in production

On 10 November 2012 01:18, rdsoze [email protected] wrote:

I think creating a new migration is better than modifying existing
migrations which currently happens when refactoring models.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6.

[rdsoze]

Even before it's in production, when there are multiple people working and they have already run their migrations, it would be a pain for everyone to just drop and recreate. A simple migration would suffice. Will you accept a PR for this ?

[jcrisp]

I'd be very happy to take your PR for this.
Can you pop it in with a -m flag for this new behaviour?
James

On 11 November 2012 17:13, rdsoze [email protected] wrote:

Even before it's in production, when there are multiple people working and
they have already run their migrations, it would be a pain for everyone to
just drop and recreate. A simple migration would suffice. Will you accept a
PR for this ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-10263632.

[redbar0n]

+1

Any progress on this?

I wouldn't want to force anyone (other developers, production, or staging) to drop the entire DB, and potentially lose data not in the seeds file, when doing a simple rename of a model.

[tgaff]

Also +1 - did you make any progress here?