On 4/22/07, John Calixto <[EMAIL PROTECTED]> wrote:
...>
> I presume, if developer A had already applied the first couple
> migrations to their testdb, they'd do something like:
>
> migration_list = [
> # 'migration1',
> # 'migration2',
> 'migration3',
>
Hi all,
I'm currently preparing my team to use Django as our primary framework
and as part of this we need a way to keep our databases in sync.
>From the Django FAQ:
> you'll have to execute the ALTER TABLE statements manually in your database.
> That's the way we've always done it, because
