Hi, that's a real bugger ... whenever a ForeignKey refers to a model that has already been defined (i.e. it is not a forward reference), the table created from it will *not* have an effective foreign key constraint. The sad details are in the ticket ...
I've tested the patch with mysql4.1, postgresql 8.1, and sqlite3. Can anybody test it with ado_mssql, please? I'm now dreaming of a test service that would automatically run the testsuite for a given patch (or multiple patches) with all supported database backends ... Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
