Greg Monroe wrote:
I also wonder if this isn't a PostGres version issue. If I remember the
SQL standards correctly, the query that PostGres is choking on is perfectly
valid SQL. PostGres, like MySQL and the like, have all been working to
follow the SQL Standard more closely. This could be a s
> I also wonder if this isn't a PostGres version issue. If I remember the
> SQL standards correctly, the query that PostGres is choking on is
perfectly
> valid SQL. PostGres, like MySQL and the like, have all been working to
> follow the SQL Standard more closely. This could be a standards bug i
ug in
your version of PostGres.
> -Original Message-
> From: Thomas Fischer [mailto:fisc...@seitenbau.net]
> Sent: Thursday, November 12, 2009 3:22 AM
> To: Apache Torque Users List
> Subject: RE: Postgresql table aliases
>
> I cannot reproduce this. When I run the DataT
I cannot reproduce this. When I run the DataTest.testUpdate in the test
project I see the following update statement in the save() method of an
updated author:
UPDATE author SET name = ? WHERE author_id = ?
Could you provide more detail how the update clause is produced ?
Thomas
> ...
> Now
