AFAIKT query_class() is only used to set the Query attribute in
django.db.models.sql.query. The relevant code part in sql.query is
# Use the backend's custom Query class if it defines one. Otherwise, use the
# default.
if connection.features.uses_custom_query_class:
Query = connection.ops.query_class(BaseQuery)
else:
Query = BaseQuery
So it's not much an issue with query_class() itself but with BaseQuery
in this module. I'd predict that it depends on the refactoring how
much this affects backends for non-relational databases at all.
Andi
On Wed, Sep 2, 2009 at 8:44 AM, Waldemar Kornewald<wkornew...@gmail.com> wrote:
>
> Hi,
> why does the backend's query_class() function get the default query
> class as its parameter? Can't the backend just import BaseQuery? I'm
> asking because with different BaseQuery implementations (for SQL and
> non-SQL) there is no real default query class, anymore.
>
> Bye,
> Waldemar Kornewald
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
