Thanks for the reply. I have posted a bug in sourceforge. Upon further investigation it looks like MAL does maintain the correct order by it expects the where cluase values first and then the values for the update from left to right. Is this the expect behaviour? I am testing with hibernate dialect (postgresql) and this clearly breaks the way the batches are handled. -Bharani Sjoerd Mullender-2 wrote:
Bharani wrote:
Hi,
I am trying to execute this sql as prepared statement
update reason set failurereason=? where ID=?
reason is a table with two columns ID is integer failurereason is a string
During the batch execution i see
exec 3('whatever',2);
in the batch and then i get
MALException:(unknown):wrong argument for prepared statement (expected int instead of char)
Looks like expected types are getting swapped.
Thanks Bharani
Looks like you're right. Can you submit a bug report in sourceforge (https://sourceforge.net/tracker/?group_id=56967&atid=482468)? Thanks.
-- Sjoerd Mullender
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- View this message in context: http://www.nabble.com/Prepared-Statement-Error-tf4116290.html#a11743621 Sent from the monetdb-developers mailing list archive at Nabble.com.