Re: Oracle schema not working

2012-06-04 Thread rahajiyev
BTW, simple db_table = 'foo' worked fine. -- 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

Re: Oracle schema not working

2012-06-04 Thread rahajiyev
My bad, folks, late in the day I forgot to add the using() clause as I'm using tiny local postgres and huge remote oracle (read mostly) and oracle won't be default. Foo.objects.using('svfe').all().order_by('-udate', '-time')[:5]; can I somehow configure it using the model? Something like in the

Re: Oracle schema not working

2012-06-04 Thread Ian
On Monday, June 4, 2012 5:36:32 AM UTC-6, rahajiyev wrote: > > Why is Django strangely quoting column and table names? It gives > Oracle syntax errors. > > DatabaseError at / > > relation "foo" does not exist > LINE 1: ...ty", "foo"."address_country" FROM "foo"."... > > Of course it exists as

Re: Oracle schema not working

2012-06-04 Thread Jani Tiainen
4.6.2012 14:36, rahajiyev kirjoitti: Why is Django strangely quoting column and table names? It gives Oracle syntax errors. DatabaseError at / relation "foo" does not exist LINE 1: ...ty", "foo"."address_country" FROM "foo"."... Of course it exists as foo, not as "foo". I already did the

Re: Oracle schema not working

2012-06-04 Thread rahajiyev
Exact error: > DatabaseError at / > > relation "foo" does not exist > LINE 1: ...ty", "foo"."address_country" FROM "foo... > -- 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

Re: Oracle schema not working

2012-06-04 Thread rahajiyev
Why is Django strangely quoting column and table names? It gives Oracle syntax errors. DatabaseError at / relation "foo" does not exist LINE 1: ...ty", "foo"."address_country" FROM "foo"."... Of course it exists as foo, not as "foo". I already did the CREATE SYNONYM trick to avoid messing with

Re: Oracle schema not working

2012-06-02 Thread akaariai
On Jun 1, 12:58 pm, Jani Tiainen wrote: > > Hello. The user connecting to Oracle is an ordinary user and needs to > > prefix all tables with the schema name. > > I've tried crafting Meta.db_table like so: > >http://cd-docdb.fnal.gov/cgi-bin/RetrieveFile?docid=3156=1... > > >

Re: Oracle schema not working

2012-06-01 Thread rihad
On Jun 1, 2:58 pm, Jani Tiainen wrote: > 1.6.2012 10:43, rahajiyev kirjoitti: > > > > > > > > > > > Hello. The user connecting to Oracle is an ordinary user and needs to > > prefix all tables with the schema name. > > I've tried crafting Meta.db_table like so: >

Re: Oracle schema not working

2012-06-01 Thread Jani Tiainen
1.6.2012 10:43, rahajiyev kirjoitti: Hello. The user connecting to Oracle is an ordinary user and needs to prefix all tables with the schema name. I've tried crafting Meta.db_table like so: http://cd-docdb.fnal.gov/cgi-bin/RetrieveFile?docid=3156=1=DjangoOracle.html But I get error

Oracle schema not working

2012-06-01 Thread rahajiyev
Hello. The user connecting to Oracle is an ordinary user and needs to prefix all tables with the schema name. I've tried crafting Meta.db_table like so: http://cd-docdb.fnal.gov/cgi-bin/RetrieveFile?docid=3156=1=DjangoOracle.html But I get error DatabaseError at / schema "foo" does not exist