On 27 juil, 13:38, Torsten Bronger <bron...@physik.rwth-aachen.de> wrote: > Hall chen! > > bruno desthuilliers writes: > > On 27 juil, 07:19, Torsten Bronger <bron...@physik.rwth-aachen.de> > > wrote: > > >> Currently, our Django app relies on the stability of various auto > >> ID fields which are implicitly generated by Django/database > >> backend. > > > [...] From a practical POV, starting from a mint empty DB and > > inserting records in the same order without any other client app > > accessing to the DB, you should probably get the same IDs, but > > there's absolutely no garantee. > > At least, they are explicitly mentioned in a "manage.py dumpdata" > fixture, and probably in a SQL dump, too. But the DB may ignore > autofields when loading that data, right?
Still a SQL DB question, but anyway: auto ID fields (at the DB level) are only autogenerated when not explicitely provided during an insert. Else - as Steve mentionned - you couldn't dump a db and restore it !-) Sorry to have forgotten about this when fisrt answering your question. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
