Hi Eduardo,
we were facing similiar issues with a heavy-load-application and torque 3.2. The application uses four connection
pools and many connections with a lot of concurrent transactions. The stack trace of the exception was the same as
yours. Other torque based applications developed by
Hi Daniel,
afaik it is neither the job of a ORM-tool nor is it possible at all to secure
such a layer against
SQL-injection. Torque does explicitly allow the usage of custom SQL. Hence some
kind of SQL-injection
is a real feature (in terms of extensibility and flexibility) in an ORM-tool
and
Hi Ivan,
I use Torque 3.0 with Postgres and have following problem:
3.0 is a little bit out-dated, isn't it? ;-)
After deleting some concrete object with usual
ClassNamePeer.doDelete(objectToDelete), I can still see it in database when
querying for that objects information with plain JDBC.
Hi,
you have to provide the used Oracle schema in build.properties, eg.
torque.database.schema = TEST
see the properties reference for details:
http://db.apache.org/torque/generator/properties-reference.html
Micha
Derek Anderson wrote:
Hey everyone,
I'm trying to generate a schema off our
hi,
use P6Spy to log all sql statements:
There already a description about configuration and usage in Torques Wiki:
http://wiki.apache.org/db-torque/FrequentlyAskedQuestions -
just look for the question How to add P6Spy for printing SQL.
You can download P6Spy from http://www.p6spy.com. It's
After a short look into several generated sources i have to agree with Alex,
imho these throws declarations are not neccessary for the mentioned
setSomeForeignKey() methods. I would appreciate if the declarations would be
removed with the next release.
so long
Micha
-Original Message-