On Wed, 2008-09-10 at 13:16 -0700, koenb wrote: [...] > As far as I can tell, this is not supported currently by the plumbing > Malcolm provided (since the operations settings eg in WhereNode are > taken from the default connection and not from the passed in > connection; this is no problem if your databases are using the same > engine, but it returns wrong SQL if you have different engines). > I allready reported this once in #7258 (which was considered invalid, > probably because I forgot to mention my use case).
This is indeed a bug (the fact that the appropriate connection isnt passed into the "where" addition), but it's a bigger one than you indicate here. The real fix will be that WhereNode.add() should be passed the "query" instance that is calling it (which contains a reference to the database connection amongst many other things). If processing a new where-constraint required, for example, adding a new table join, you're out of luck at the moment. I'm holding off committing this until we branch off the 1.0-bugfixes branch, since it's only going to go onto trunk (it's essentially a feature-add). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
