Re: I can't decide on a migration framework

Thanks Russ! Your insight is greatly appreciated. On Mon, Mar 9, 2009 at 8:58 PM, Russell Keith-Magee wrote: > > On Tue, Mar 10, 2009 at 8:23 AM, Ben Davis wrote: > > are you saying that django-evolution does not support migrating between > >

Re: I can't decide on a migration framework

On Tue, Mar 10, 2009 at 8:23 AM, Ben Davis wrote: > are you saying that django-evolution does not support migrating between > "versions"  (ie up and down)? Django Evolution doesn't currently support down-migrations. This isn't due to any particular technical limitation -

Re: I can't decide on a migration framework

On Tuesday 10 March 2009 04:53:25 Ben Davis wrote: > are you saying that django-evolution does not support migrating between > "versions"  (ie up and down)? no > > I'm mostly trying to get an idea of what migration frameworks django > devopers use, and why they prefer it. most do not use

Re: I can't decide on a migration framework

are you saying that django-evolution does not support migrating between "versions" (ie up and down)? I'm mostly trying to get an idea of what migration frameworks django devopers use, and why they prefer it. On Mar 7, 2009 5:31 PM, "Briel" wrote: A fixed migration is the

Re: I can't decide on a migration framework

A fixed migration is the code run to get from one step to another. Migrations uses the, maybe at some point you needed to add an extra table to the db. Then you could write a migration that would add the table if you wanted to progress or delete the table if you wanted to get back. You would have

I can't decide on a migration framework

I've been looking into both the "South" and "django-evolution" migration frameworks. There are things I like about both of them, although I'm leaning towards django-evolution. The thing I like about django-evolution is that migrations are described in the same "language" as your model, that