On Jan 14, 2008 11:46 PM, knight <[EMAIL PROTECTED]> wrote: > > I have a large fixture initial_data.xml and I'm trying to syncdb on > new Postgres database, & though it says it imported 764 objects, I see > none in the db.
As another reply suggests - if your fixture loading operation is returning 'imported 764 objects', they are being loaded, its just a matter of where. > After a little investigation, I think it is related to dependencies > between classes (foreign keys), which aren't handled in the right > order. Unlikely. We have a fairly extensive test suite for fixture loading, and we explicitly test for potential order dependency issues. > I'm using Python 2.3.5, Postgres 8.1.2 & Django dev version. > Is this a known issue? Is it related to Postgres or its DB API? To the best of my knowledge, there are no fixture loading problems with the Postgres backend. Postgres is probably the most reliable of the backends for fixture loading. That doesn't mean there _isn't_ a bug - just that it would be the backend that is least likely to have one. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
