#8 getCatalog and setCatalog

[Brian McAnulty]

jdbcConnection.setCatalog just ignores the call - would
be nice if it actually tried to call this on the
underlying JDBC driver. Similarly, getCatalog returns
null, without even trying.

Can these be changed to perhaps call the underlying
JDBC driver and catch an exception, returning null in
the case of getCatalog or even just passing up the
exception? Not sure why you'd want to smother these
calls?

(We need the catalog name as the driver we're using for
mysql (twz1) won't perform databasemetadata calls like
getColumns() without it...At present we call
getCatalog() and pass this value in, would be nice not
to have to get the DB connection object and get it from
there...)

[Brian McAnulty]

Logged In: YES
user_id=897302

Following on....

getColumns explicitly rejects any requests (throws an
Exception) specifying a catalog anyway, which seems a bit
harsh!

[Thomas Mueller]

Logged In: YES
user_id=15973

You should not need the catalog name for getColumns, as LDBC
works with null catalog name for getColumns. Actually, LDBC
works only with null catalog name. For LDBC, the databases
don't have and don't support catalogs. That's why an
exception is throws when trying to use catalogs.