On 24/01/2014 8:03am, Alex Thomas wrote:
I have already created a stackoverflow question on this and have only
received one (*incorrect*) response. For the sake of time I am just
linking that question which has all the details.
http://stackoverflow.com/questions/21151544/django-loaddata-with-natural-keys-not-querying-correct-forign-key
Is it possible that voyage_id is the problem?
https://docs.djangoproject.com/en/1.6/topics/serialization/#topics-serialization-natural-keys
That documentation says that the natural key must be unique and you need
either unique=True for a single field or a meta attribute of
unique_together nominating those fields you want as the natural keys.
Have you tried unique=True for voyage_id?
If that doesn't work, maybe you can pair it with another value or values
which would be unique together.
Mike
-Alex
-- You received this message because you are subscribed to the Google
Groups "Django users" group. To unsubscribe from this group and stop
receiving emails from it, send an email to
django-users+unsubscr...@googlegroups.com. To post to this group,
send email to django-users@googlegroups.com. Visit this group at
http://groups.google.com/group/django-users. To view this discussion
on the web visit
https://groups.google.com/d/msgid/django-users/8a619cdb-1ac4-474b-8d6e-ef45825c418b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/52E1CD67.3000501%40dewhirst.com.au.
For more options, visit https://groups.google.com/groups/opt_out.
