Anyway, look at the query that needs to be executed. This doesn't
contain any joins. The only problem is that this perfectly correct
query is send to wrong schema although the router suggests a good one.
I don't know why, is there anyone who can explain this to me?
--
You received this message be
Unfortunately not exactly.
Schema in Oracle is a synonym of user so you need name and password.
That's why it doesn't fit into tablespaces solution you pointed.
There is open ticket about support for multiple schemas but it's still
unfinished.
This is why I was looking for solution that would work
Sorry, I've just found that schema != tablespace, so my last response is
irelevant...
Cheers,
Tom
Dne pátek, 12. října 2012 19:26:53 UTC+2 Tomáš Ehrlich napsal(a):
>
> Hi Michał,
> is "schema" the same as thing as "tablespace"? If so, you should define
> them using
> db_tablespace meta keywo
Hi Michał,
is "schema" the same as thing as "tablespace"? If so, you should define them
using
db_tablespace meta keyword.
https://docs.djangoproject.com/en/1.4/topics/db/tablespaces/
DATABASES creates new database connection and it's really not
possible to make relations between databases.
Cheer
First of all the error is not from django but from database.
Secondly I'm not using different databases but different schemas so
relations are possible.
The error has nothing to do with foreign key or any relation.
It just looks like django is ignoring router suggestion and directs
sql query to wro
On Fri, Oct 12, 2012 at 4:54 PM, mnowotka wrote:
> I have django running on oracle backend. I need to use two schemas - one for
> a legacy DB, second one for all django related tables.
>
> So this is my settings.DATABASES:
>
> DATABASES = {
>
> 'default' : {
> 'ENGINE': 'django.db.back
I have django running on oracle backend. I need to use two schemas - one
for a legacy DB, second one for all django related tables.
So this is my settings.DATABASES:
DATABASES = {
'default' : {
'ENGINE': 'django.db.backends.oracle'
'NAME': 'django',
7 matches
Mail list logo