Hi There,
I've had similar problems and it comes down to the line in query.py that
looks in backend and sets QuerySet to _QuerySet or backend.QuesrySet if
there is one... I've also written some code to mitigate against this, and
I'd suggest anyone with an interest gets together on this so that we'r
On Oct 17, 1:29 pm, Carlos Hanson <[EMAIL PROTECTED]> wrote:
> On Oct 17, 12:33 am, koenb <[EMAIL PROTECTED]> wrote:
>
> > 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.
>
> > K
On Oct 17, 12:33 am, koenb <[EMAIL PROTECTED]> wrote:
> 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
I've installed the latest patches for multi-db agains revision 645
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 Q
On Oct 16, 6:38 pm, Carlos Hanson <[EMAIL PROTECTED]> wrote:
> I am having trouble with Django revision 6110 patched with multi-
> db-6110.patch.
>
> Traceback (most recent call last):
> File "", line 1, in ?
> File "/usr/local/lib64/python2.4/site-packages/django/db/models/
> query.py", line
Sorry Carlos,
those patches are far from complete, and I don't use Oracle myself.
For the moment the backends in the patches use the following to get
the connection:
connection = self.model._default_manager.db.connection
Removing the import and putting in that line should do the trick.
6 matches
Mail list logo
