Re: pgadmin vs schema migration

Thanks. It's good to get a little second opinion. I'm sure I'll make
the switch to migration tools eventually as things become a little
more involved.

Cheers
gav

On Feb 24, 11:58 am, Mike Ramirez <gufym...@gmail.com> wrote:
> On Thursday, February 24, 2011 03:48:18 am ggavy wrote:
>
> > Hello everyone,
> >     if I have a live app running off a postgres db (containing data)
> > and I want to make reasonably simple schema (and possibly data
> > content) changes, are there any dangers in just using pgadmin (e.g
> > adding a column) as opposed to using some type of migration software,
> > e.g. south. I'd keep my models.py up-to-date with any changes I make
> > to the database (in case of future uses of the app). I haven't seen
> > anything online warning me not to do it, but the separation worries me
> > slightly
>
> > Thanks
>
> prior to the migration systems (south/evolution) and even after that for
> awhile, it was the defualt way, to manage it manually. The migration tools
> just make it easier.
>
> As long as you keep your table and model definitions, and create/insert/update
> statements all in line, it's safe.
>
> Personally,I'm with all the others and suggest you use migration tools, unless
> this is a one off and not going to be doing this a lot, Then I do find it just
> faster and easier to do it manually.
>
> Mike.
>
> --
> Vermouth always makes me brilliant unless it makes me idiotic.
>                 -- E.F. Benson

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.