db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Hilka" <thi...@vps.de>
Subject AW: Logging of sql statements of a single peer class
Date Tue, 11 Dec 2007 10:50:21 GMT
Hi Thomas,

thank you for your answer. 

But there is a problem with this solution. The sql statements are generated
somewhere inside torque, not in the peer classes. If I have a criteria in
the peer classes, I can get most of the information from this criteria. But
if I do a BaseRecord.save(), which is actually outside of the peer class,
but in the same layer, I don't have the information how the sql statements
looks like.

The straightforward solution would be to log everything and then filter the
logfile for the parts we are interested in. But this is not very elegant
either.

Tobias

-----Urspr√ľngliche Nachricht-----
Von: Thomas Fischer [mailto:fischer@seitenbau.net] 
Gesendet: Dienstag, 11. Dezember 2007 10:27
An: Apache Torque Developers List
Betreff: Re: Logging of sql statements of a single peer class

> is there any possibility to log only the sql statements triggered by a
single
> Peer class? I know that there are logging functionalities concerning
BasePeer.
> But with these, all sql expressions are logged, not only the ones
triggered by
> the single Peer class.

I know this is not the most elegant way, but you can add logging
functionalities to the peer in question and then configure log4j (or
whatever logging framework you are using) to discard the logging of base
peer and only use the loggin in your peer class.

     Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message