You can use a logging driver such as p6spy to see your SQL statements.
http://sourceforge.net/projects/p6spy/
On 19 January 2012 08:25, Thomas Fox thomas@seitenbau.net wrote:
Perhaps you can use the log output (with some tweaks to the log4j
configuration). However I'm not sure how and if
On 7 July 2010 21:32, Graham Leggett minf...@sharp.fm wrote:
On 07 Jul 2010, at 4:43 PM, Greg Monroe wrote:
Torque has been using Village pretty much since day 1.. and AFAIK the
Village has been using metadata as long. If you didn't have performance
problems before, it's probably a JDBC
For the latest versions of 1.4.2 (_10 and up) and 5/6 there is a very
useful utility called jmap -
http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html
that's built into the Java SDK. This dumps out all the objects in the heap.
Doesn't work under windows though..
Joe
On 30/12/06, Thomas
I can confirm that the ant scripts work fine in Eclipse.
Don't forget the build.properties though - which eclipse
does confuse with plugins but just click the plain text edit
or use a different name in the ant build file.
Remember to press F5 (refresh) after a generate too! :-)
We use WTP 1.5
Certainly for Sybase it's set via the database itself.
It's independent of Torque.
We moved to UTF-8 to avoid charset issues.
Joe
On 06/09/06, Thomas Fischer [EMAIL PROTECTED] wrote:
Hi,
I do not know of a feature of Torque that allows setting the encoding of
characters sent to the database.
We explicitly laod the properties file and pass the Configuration into
Torque.init
by using PropertiesConfiguration files. See Apache commons Configuration.
I sure there's more details of how to load and debug the file loading there.
It's most likely looking in your current directory.
Joe
On
Shouldn't your classes be in WEB-INF/classes not WEB-INF/src?
Joe
On 23/06/06, Norbert Kunstek [EMAIL PROTECTED] wrote:
Hello,
I have all the required jar-files in the WEB-INF/lib directory (torque
runtime + dbdriver).
My Torque.properties is in the WEB-INF directory.
I have the
The alternative is to use a JDBC driver like p6spy.
This puts itself between Torque and the real driver.
Has the advantage of getting any JDBC written by hand too.
Works very well - but don't use it on a production server as it leaks like a
sieve!
Joe
On 08/06/06, Eustache [EMAIL PROTECTED]
-Original Message-
From: Thomas Vandahl [mailto:[EMAIL PROTECTED]
Sent: 24 May 2006 16:50
To: Apache Torque Users List
Subject: Re: Prepared statements
Joseph Carter wrote:
We're doing some performance testing on Torque and we've
noticed that
it doesn't seem to use prepared statements.
