Bug 76600 - Don't use DatabaseMetadata
Don't use DatabaseMetadata
Status: NEW
Product: db
Classification: Unclassified
Component: DB schema
5.x
All All
: P2 (vote)
: TBD
Assigned To: Libor Fischmeistr
issues@db
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-19 10:46 UTC by kovica
Modified: 2013-08-01 12:53 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kovica 2006-05-19 10:46:14 UTC
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.
Comment 1 Andrei Badea 2006-05-19 13:38:01 UTC
Thank you for the offer to help. I will let you know when I start to work on the
dbschema replacement again.
Comment 2 Jiri Rechtacek 2009-10-16 14:08:15 UTC
Reassigned to new owner.
Comment 3 matthias42 2013-05-18 21:32:24 UTC
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.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo