Malcolm Tredinnick wrote: > At some point in the future, multi-valued ON constraints might make an > appearance (for example, multi-column primary key queries are possibly > easier to write), but they might not, too. The slight preference for > doing so at some point is that there are a couple of cases on some > databases where join constraints are handled more efficiently than where > constraints. Well, that's what i am trying to do, only construct ON contraints for composite primary keys, nothing else.
Anyway, thanks for your insightful reply. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
