On 19 Paź, 12:00, bruno desthuilliers <bruno.desthuilli...@gmail.com>
wrote:
> On 18 oct, 23:15, Mike Ramirez <gufym...@gmail.com> wrote:
>
> Or write a custom migration script, or just fire your favorite db
> client and issue a couple SQL queries.
>
> > I tend to start with the models first and when I add a field, I just use
> > alter
> > to update the table in place. This has a gotcha with NOT NULL though, if you
> > don't specify a default you'll end up with an error. To bypass this error,
> > I
> > usually don't add the NOT NULL constraint till after I've added the field
> > and
> > updated the existing rows with the required data.
>
> > This may not be the best approach to it, but it works for me and is fast
> > enough and requires less prep time for using such tools as evolution and the
> > like (no need to install or learn them) and/or editting fixtures.
>
> +1
I was also migrating manually, but after I started using
http://south.aeracode.org/
now I could not imagine going back to doing manual migrations.
--
Tomasz Zielinski
http://pyconsultant.eu
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
