On Fri, Oct 23, 2009 at 5:09 AM, Thomas Wanschik <twansc...@googlemail.com> wrote: > >> When a new QuerySet is instantiated (e.g. by calling >> Model.objects.all()) it asks the backend for its Query class and then >> creates an instance of that class. By default, this class is >> sql.Query. Only the Oracle backend has its own Query which subclasses >> sql.Query. > > I think Waldermar wanted to say: 'Only the Oracle backend has its own > Query which subclasses sql.query.BaseQuery.' instead of 'sql.Query'.
I should point out that this is one of the specific problems Alex and I are trying to address in the multi-db refactor. When we've finished, returning the right query class should be as simple as implementing an API on the backend. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
