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.

Bug 111055 - Database Application shell causes Oracle table analysis
Summary: Database Application shell causes Oracle table analysis
Status: RESOLVED WONTFIX
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
: 66471 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-07-26 09:32 UTC by davmacbea
Modified: 2009-11-02 11:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description davmacbea 2007-07-26 09:32:56 UTC 
In Netbeans IDE 6.0 M10 (build 200706281431) the New Project Wizard has an option to create a "Java Desktop 
Application".  When this is chosen the user then gets the opportunity to select an application shell.  If "Database 
Application" is chosen the user can then select a DB connection, a table, columns and a detail table.  Once this has 
been done and the project has been created a significant change has been made to my database.

We run Oracle 8.1.7 and use rule-based optimization as opposed to cost-based optimization. When the new project was 
completed Netbeans had issued sql to Oracle to carry out cost-based analysis on the parent and detail tables.  This 
has a huge impact on our system (the development environment version of the web application that used the tables in 
question effectively stopped functioning due to hugely increased SQL execution times).  Instructions to the database 
to carry out analysis like this should not be issued behind the scenes without any warning to the user.  I could not 
find an option to alter this behaviour.

Our JDBC driver is the Oracle ojdbc14.jar.
Comment 1 Andrei Badea 2007-07-26 12:42:19 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
Comment 2 David Vancouvering 2008-01-10 00:53:53 UTC 
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.
Comment 3 David Vancouvering 2008-10-09 18:55:14 UTC 
*** Issue 66471 has been marked as a duplicate of this issue. ***
Comment 4 David Vancouvering 2008-11-12 17:42:35 UTC 
Maybe we can fix this with our metadata rewrite, where we have the opportunity to override things for a specific
database vendor.
Comment 5 Jiri Rechtacek 2009-02-10 15:39:34 UTC 
Reassigned to new owner.
Comment 6 Jiri Rechtacek 2009-05-12 13:51:59 UTC 
No plan to fix it in a present time.
Comment 7 Quality Engineering 2009-11-02 11:17:52 UTC 
NetBeans.org Migration: changing resolution from LATER to WONTFIX