It seems like multi-table sub-classed models (not abstract) don't honor the "pk" being specified in fixtures. For example, I have an Event class that is sub-classed by a Race model. The Event class is in an app called "calendar" and the Race model is in an app called "regattas". I dumpdata regattas, reset both apps, and loaddata the regattas fixture. It loads properly but all of the PKs are now sequential, meaning a lot of other models are now pointing at the wrong regatta entry. There were regattas with IDs 14, 16, and 18, but are now 1, 2, and 3. I have confirmed that the fixture contains the old 14, 16, and 18 primary keys.
The problem is the keys seem to be compacted rather than being loaded from the fixture. The keys are not always sequential due to deletes. So the problem doesn't exhibit itself until you delete, dumpdata, then try to re-load. Does anyone have any good way to get around this problem? It's somewhat of a show-stopper for us. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
