Aymeric, No problem. Thanks for the replies. I just created the ticket @ https://code.djangoproject.com/ticket/20666
On Wednesday, June 26, 2013 2:27:03 AM UTC-4, Aymeric Augustin wrote: > > Thanks for taking the time to check. Based on Russell's message, I think > that's a bug, but I'm not sure why it happens. Could you file a ticket in > the tracker, so we don't forget about it? > > Thank you, > > -- > Aymeric. > > On 26 juin 2013, at 02:43, Yo-Yo Ma <[email protected] <javascript:>> > wrote: > > > It does happen in 1.5, but the error is somehow slightly different (no > traceback in 1.5 to find the root cause). I have 2 fields on the order > model pointing to the address model. I included only the one in my above > example because it was consistently the culprit (likely due to being > defined above the other). In 1.5 the *other* field is consistently the > culprit: > > > > IntegrityError: Problem installing fixtures: insert or update on table > "orders_order" violates foreign key constraint > "shipping_rate_id_refs_id_84a732cf" > > DETAIL: Key (shipping_rate_id)=(2) is not present in table > "shipping_shippingrate". > > > > The error on 1.6 again is: > > > > django.db.utils.IntegrityError: Problem installing fixture > '/opt/myproject/apps/orders/fixtures/test_data.json': Could not load > orders.Order(pk=1): insert or update on table "orders_order" violates > foreign key constraint "bill_address_id_refs_id_3a4d3fef" > > DETAIL: Key (bill_address_id)=(1) is not present in table > "orders_orderaddress". > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
