This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Database Application shell causes Oracle table analysis | ||
---|---|---|---|
Product: | db | Reporter: | davmacbea <davmacbea> |
Component: | Code | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
davmacbea
2007-07-26 09:32:56 UTC
Not NetBeans is to blame, but the Oracle driver. It issues an ANALYZE TABLE statement as part of the implementation of the DatabaseMetaData.getDriverInfo() method. Even if we call getDriverInfo() with the "approximate" parameter set to true, it still issues the ANALYZE TABLE statement. Not sure we can do anything about it apart from not calling getIndexInfo() -- which we don't want to do. Perhaps write our own query instead of calling getIndexInfo(). See also http://forums.oracle.com/forums/thread.jspa?threadID=210782 I'll see how hard it is to write our own query... If it's not possible, I'll need to close this saying WONTFIX, but let's give it a go first. *** Issue 66471 has been marked as a duplicate of this issue. *** Maybe we can fix this with our metadata rewrite, where we have the opportunity to override things for a specific database vendor. Reassigned to new owner. No plan to fix it in a present time. NetBeans.org Migration: changing resolution from LATER to WONTFIX |