That's the nasty edge case - currently it just fails, in the new system
it'll generate three migrations (add A with no FK; add B with FK; add FK to
A). As for the previous post, the syncdb-like step will always run before
the migration step; thus, dependencies are allowed from a migrated to a
non-m
On 05/31/2013 09:55 AM, Mantas wrote:
Quoting django-developers@googlegroups.com (2013-05-31 07:39:24)
From: Andrew Godwin
Date: May 30 07:03PM +0100
Url: http://groups.google.com/group/django-developers/msg/137ab14f361fd052
2. Leave syncdb as it is, like South does, and have everything happen
Quoting django-developers@googlegroups.com (2013-05-31 07:39:24)
> From: Andrew Godwin
> Date: May 30 07:03PM +0100
> Url: http://groups.google.com/group/django-developers/msg/137ab14f361fd052
>
> 2. Leave syncdb as it is, like South does, and have everything happen
> through a "migrate" command.
