In the latest patches for multi-db the QuerySet that is returned is no longer fixed, but varies with the model's manager. That should fix that problem for now.
Koen On 17 okt, 09:03, Ian <[EMAIL PROTECTED]> wrote: > I don't know anything about the multi-db branch, but I imagine that > whatever QuerySet does to get the correct connection should work in > OracleQuerySet as well. > > Note the mere existence of OracleQuerySet will still be problematic in > multi-db environments that mix Oracle databases with non-Oracle > databases, since OracleQuerySet replaces QuerySet entirely when Oracle > is used. However, OracleQuerySet is a hack that will be going away > after the QuerySet refactor, which solves both problems in the long > run. > > Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
