proxool-developer

[Proxool-developer] SQL statement from the Conncetion

[xyz a. <vik...@ho...>]

Hello ,
I was looking at ConnectionListenerIF's onExecute method. The note says that
command is not fully implemented at this stage. At some point it might 
represent the SQL that is sent to the database (or the procedure call that 
was used). Is that something being considered in a very near future? If we 
implement the method,is there any way to get the SQl query out of a 
connection associaited with that query( through Statemnent). 
java.sql.Connection class does not have a  method like conn.getStatement(). 
Would such methods be possible in ProxyConnection?

Thanks in advance
Vick

_________________________________________________________________
Is your computer infected with a virus?  Find out with a FREE computer virus 
scan from McAfee.  Take the FreeScan now! 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

Re: [Proxool-developer] SQL statement from the Conncetion

[Bill H. <bi...@lo...>]

Hi Vick,

On Thu, 2003-11-13 at 19:56, xyz abc wrote:

> I was looking at ConnectionListenerIF's onExecute method. The note says that
> command is not fully implemented at this stage. At some point it might 
> represent the SQL that is sent to the database (or the procedure call that 
> was used). 

I'm pleased to say that the documentation is wrong. It *is* implemented
:)

The SQL should pretty accurately represent what was sent to the
database. Almost like a journal. I say things like "should", and
"pretty" and "almost" because it's not thoroughly tested. There are lots
of ways of constructing statements and executing SQL in the JDBC API and
we've have attempted to trap them all. 

So, my recommendation is: please use the onExecute() method and let us
know if you have any problems. I have not come across any yet.

The onExecute() method is the only way to extract the SQL from the
connection. Note that it might contain a semicolon delimited list of
queries if a batch execute was used.

Regards.
Bill Horsman