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.
There is plenty more wrong (certainly with that 6110 patch, the 6453
one is a little better), but I haven't had the time to work on it
further.
Koen
> The problem seems to be in django/db/backends/oracle/base.py on line
> 92:
>
> from django.db import connection
>
> which is later used to get the cursor. This seems to bypass the use
> of the database settings in OTHER_DATABASES. I would expect to use
> connections from django.db rather than connection:
>
> # Create a manager for named connections
> connections = LazyConnectionManager()
>
> # Backwards compatibility: establish the default connection and set
> the
> # default connection properties at module level, using the lazy
> proxy so that
> # each thread may have a different default connection, if so
> configured
> connection_info = LocalizingProxy('connection_info', _local,
> lambda: connections[_default])
> connection = LocalizingProxy('connection', _local,
> lambda:
> connections[_default].connection)
>
> But I don't see how to get the named connection in oracle/base.py.
>
> If that is clear, I would appreciate any suggestions.
>
> Carlos Hanson
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
