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:
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
