On 7/22/07, james_027 <[EMAIL PROTECTED]> wrote: > > the profile table's dell has constraint clause in it, while the > cellusage table has no constraint clause only key clause is only tells > that it is index.
That appears to be the effect of ticket #2720 [1] that I mentioned earlier. The foreign key column _is_ getting created - it's the _constraint_ that isn't created correctly, depending on the order of creation. Even more annoying - they syntax to create the constraint actually _is_ generated - but MySQL ignores it. There is a proposed patch to fix this problem attached to the ticket. I haven't looked at the patch, so I have no idea how good it is, or if it solves the problem. This is a bug, and one of these days one of the core developers will hopefully get around to looking at it. However, in practice, the existence of this bug won't make much difference to you, especially as you are just starting out with Django. It won't affect the views Django produces, or the queries you can execute. Django's ORM framework will provide some protection from putting invalid data into the database - having the constraint in place acts as extra support to make sure nothing goes wrong. If you need row-referential integrity _now_, I can only suggest using a different database backend (MySQL has a few other annoying issues that can pose difficulties). For future reference: It would have been possible to resolve this issue in 1 or 2 emails if you had provided the SQL dump in the first place. It sounds like you had this SQL dump from the very beginning, but it took 6 emails for you to share this information with me. Repeatedly saying "X doesn't work" doesn't help me (or anyone else) debug a problem. On the other hand, stack traces, precise instructions, or other debug printouts are very helpful. Help us to help you, and everyone can go home early :-) [1] http://code.djangoproject.com/ticket/2720 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 -~----------~----~----~----~------~----~------~--~---
