DbLoaderTst bombs out with all sorts of erros (OOM, duplicate tables etc.)
when run against Oracle and the connection's user has the 'DBA' role; in
Modeler this is not a problem since the schema name is explicitly picked.
Does anybody know if there's a way to get the user's preferred schema (if
there is such a thing?) or should we just have DbLoaderTest access a
'CAYENNE' schema (line 102, instead of 'null' schema name for getTables())
for the test and get over it? Would this affect DBs without schema
support? Postgres as of 7.3 got schema support as well, so the problem
would not be Oracle-specific..
Holger
This archive was generated by hypermail 2.0.0 : Tue Feb 04 2003 - 11:15:38 EST