🚀 go-pugleaf

Tim Truman wrote:

> 
>>Hint: Try Squirrel. Does it exhibit the same behavior?
>>http://squirrel-sql.sourceforge.net/
> 
> Yes. When the metadata indexes tab is selected.
> 
> Scary.
> 
> But I would guess the code could be modified to eliminate this behavior.
> 
> > It would seem the only way to quickly solve the issue is to provide a
> single user account for each developer and grant in the objects they need
> access to. Keeping access to production schemas off limits. I am perplexed
> however as to why these tools issue commands that affect the operation
> behavior of the database. ANALYZE is a well documented command affecting
> the operation of the CBO.
> 
> In any event, thank you Paul (TeamB) for taking interest in my issue and
> providing assitance. It is appreciated.
> 
Tim,

You may get the developers (or you) to try using the Oracle drivers for your
connections, rather than the java.sql drivers and use the Oracle Drivers.

For instance, try typecasting the Connection.getMetaData() with

OracleDatabaseMetaData dmd =
(OracleDatabaseMetaData)connection.getMetaData();

Check through the dmd instance of OracleDatabaseMetaData. See if it will
return the ANALYSE option. If so, you can probably change this value using
the API. 

I am willing to wager that most tools are using the Connection classes
getMetaData() from the java.sql package, which probably uses only default
settings and does not allow overrides to these methods or accessor methods
(sets) for database vendor specifics (such as those in Oracle). However,
the Oracle drivers may allow for this directly. Since I am not at work, and
I do not have Oracle at home, I cannot test my theory. I will do so this
week (when I get some time) and let you know what I find, if you do not
beat me to it :)

Good luck (to both of us).