The Criteria clone method comes from its Hashtable superclass. The problem
is probably because Hashtable is doing a shallow copy and the underlying
objects are the same. FWIW, there is a JIRA wish list item for this to be
redone as a deep copy. But this probably will be a 4.0 item.
In
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 version problem.
FWIW, getting rid of Village (or highly modifying it) is a 4.0 goal. But
AFAIK, the Village use
I had a very similar problem (if not the same), using the wrong version of
Postgres ODBC drivers (not from Java...).
Try with a different version of the driver...
Regards,
Álvaro
From: Greg Monroe greg.mon...@dukece.com
To: Apache Torque Users List
...
Has anyone encountered this before and managed to work out how to stop
the metadata queries being translated into database queries? I would
expect either the JDBC driver to cache these, or if not for Village to
cache these.
I remember dimly using a patched version of village which
On 07.07.10 19:15, Thomas Fischer wrote:
...
Has anyone encountered this before and managed to work out how to stop
the metadata queries being translated into database queries? I would
expect either the JDBC driver to cache these, or if not for Village to
cache these.
I remember dimly
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 version problem.
I've just methodically tried the postgresql
