Re: Stability of auto IDs

On 7/27/2010 12:38 PM, Torsten Bronger 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?
>
It couldn't do that without ruining the relationships, could it? A dump
includes the numerical values for the foreign keys, so the related
primary keys have to stay the same to maintain relational integrity.

regards
Steve

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.