[sqlalchemy] Re: Error after upgrade from 0.4.3 to 0.4.6

2008-07-21 Thread shday

Hi,

I've done some exploring and found that if I connect to the database
as the schema owner the error goes away. I had been connecting through
a proxy account and this was working fine in 4.3. You can see where
this is tripping up 4.6 from the sql log just after staring the app:

With 4.6:

C:\Documents and Settings\daystev\Desktop\asrt_trunk\srt-projectstart-
srt.py dev.cfg
SELECT USER FROM DUAL
{}
select COLUMN_NAME, DATA_TYPE, DATA_LENGTH, DATA_PRECISION,
DATA_SCALE, NULLABLE
, DATA_DEFAULT from ALL_TAB_COLUMNS where TABLE_NAME = :table_name and
OWNER = : owner
{'owner': 'ASRT_PROXY', 'table_name': 'ACC_PROTOCOL'}
Traceback (most recent call last):
  File C:\Documents and Settings\daystev\Desktop\asrt_trunk\srt-
project\start-srt.py, line 24, in module
...

With 4.3:

C:\Documents and Settings\daystev\Desktop\asrt_trunk\srt-projectstart-
srt.py dev.cfg
SELECT USER FROM DUAL
{}
select COLUMN_NAME, DATA_TYPE, DATA_LENGTH, DATA_PRECISION,
DATA_SCALE, NULLABLE
, DATA_DEFAULT from ALL_TAB_COLUMNS where TABLE_NAME = :table_name and
OWNER = : owner
{'owner': 'ASRT_PROXY', 'table_name': 'ACC_PROTOCOL'}
Traceback (most recent call last):
  File C:\Documents and Settings\daystev\Desktop\asrt_trunk\srt-
project\start-srt.py, line 24, in module
...

Note that 4.6 is using ASRT_PROXY as the owner while 4.3 uses ASRT
(the actual owner).

To fix the problem (and continue using the proxy account) I added
schema=ASRT to all my table definitions. Now everything works fine.

Thanks for all your work. Congrats on the book(s)!

Steve





On Jul 18, 1:45 pm, Michael Bayer [EMAIL PROTECTED] wrote:
 On Jul 18, 2008, at 1:32 PM, shday wrote:



  I upgraded from 0.4.3 to 0.4.6 and now I get the error below when
  starting my TurboGears app. I'm using reflection and that fails on the
  first table. I had a look at the changelog and tried adding
  oracle_resolve_synonyms=True to that table's definition but I got
  another error (not shown here).

  Any help would be appreciated.

 what's the schema look like ?  are synonyms in use ?  are there cross-
 owner names in use ?   what's the error you got with
 oracle_resolve_synonyms ?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---



[sqlalchemy] Re: Error after upgrade from 0.4.3 to 0.4.6

2008-07-18 Thread Michael Bayer


On Jul 18, 2008, at 1:32 PM, shday wrote:


 I upgraded from 0.4.3 to 0.4.6 and now I get the error below when
 starting my TurboGears app. I'm using reflection and that fails on the
 first table. I had a look at the changelog and tried adding
 oracle_resolve_synonyms=True to that table's definition but I got
 another error (not shown here).

 Any help would be appreciated.


what's the schema look like ?  are synonyms in use ?  are there cross- 
owner names in use ?   what's the error you got with  
oracle_resolve_synonyms ?



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---