For that to happen, models would have to be changed without a migration being generated, or without it boeing added to source control. Neither is good practice. On Aug 16, 2012 7:56 AM, "Benjamin Lei" <benlei1...@gmail.com> wrote:
> I'm just wondering since it seems the migrations created are all prepended > with an incremental number... so if two developers were to push two > different migrations, each with the same id, I'm afraid something bad will > happen. > > For example: > Dev A: creates 001_somedesc > Dev B: creates 001_someotherdesc > Dev A: commits 001_somedesc into repo > Dev B: commits 001_someotherdesc into repo > > Is it better to just use the default django "syncdb"? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/KPdf40hcre0J. > 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. > -- 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.
