On Fri, Sep 11, 2009 at 2:51 PM, Waldemar Kornewald
wrote:
>
> On Sep 3, 4:06 pm, Russell Keith-Magee wrote:
>> Adding non-SQL backends into the mix complicates things a little
>> further, since a query could be directed at a non-SQL backend. Working
>> out exactly how to handle this sort of eve
On Sep 3, 4:06 pm, Russell Keith-Magee wrote:
> Adding non-SQL backends into the mix complicates things a little
> further, since a query could be directed at a non-SQL backend. Working
> out exactly how to handle this sort of eventuality is one of the
> things I want to look at during the sprint
On Thu, Sep 3, 2009 at 4:21 PM, Waldemar Kornewald wrote:
>
> Also, when will your branch be merged into trunk? Is there any
> roadmap?
When It's Done (tm) :-)
I would like to think this is on target for v1.2, but that does depend
somewhat on solving one or two outstanding design issues. So,
op
Hi Alex,
On Sep 2, 5:47 pm, Alex Gaynor wrote:
> As Russ says this is something causing problems for multi-db. I think
> it's important to recognize that there are 2 "types" of backends,
> something like Oracle/DB2/MsSQL that is fundamentally the same
> architecture as the existing SQL backend
On Wed, Sep 2, 2009 at 10:47 AM, Russell
Keith-Magee wrote:
>
> On Wed, Sep 2, 2009 at 2:44 PM, Waldemar Kornewald
> 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 wi
On Wed, Sep 2, 2009 at 2:44 PM, Waldemar Kornewald 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
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.que
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
--~--~-
