I know from my own experience that using DatabaseMetadata to retrieve informatin
about database, tables, primary keys, ... is VERY VERY slow. At least with DB2.
I suggest that you read those information by querying system catalog. I know
that DatabaseMetadata is the standard way, BUT the performance would be 10x
better, if not more. So supporting databases with thousends of tables would not
be a problem anymore (look at issue 76063).
I'm willing to help.
Thank you for the offer to help. I will let you know when I start to work on the
dbschema replacement again.
Reassigned to new owner.
This should be filed against the JDBC drivers at the vendors bug tracking system. If there is a fast way to retrieve database metadata and the driver does not use it, an application should not work around this defiancy (IMHO).
The JDBC driver abstracts access to the database metadata, removing this abstraction will make life painful. You will need to write code for each DBMS and probably do work-arounds for version specific quirks.
*** Bug 252907 has been marked as a duplicate of this bug. ***