#13 Bad syntax of SQL statements logged

open
nobody
None
5
2013-10-12
2005-02-02
Emmanuel
No

Prepared statements are not correctly logged.
The sql statement is not the same as the one executed
by the Database.

example :
1. Prepared statement definition
UPDATE orders SET OPPOSITECOUNTRY = ? , overseadate = ?
, hazardousdetails = ? , CONTACTNAME = ? , CONTACTFAX =
? , CONTACTEMAIL = ? , CONTACTREMARKS = ? ,
CONTACTPHONE = ? , containerno = ? , sealno = ? ,
PRESETMODE = ? , CUSTOMSTDOCU = ? , CUSTOMSINSTRUCTION
= ? , REMARKS = ? , vatid = ? , loadrequest = ? ,
lastvalidationstartdate = ? WHERE id = ?

2. Prepared statement execution
UPDATE orders SET OPPOSITECOUNTRY = '' , overseadate =
'' , hazardousdetails = '' , CONTACTNAME = '' ,
CONTACTFAX = '' , CONTACTEMAIL = '' , CONTACTREMARKS =
'' , CONTACTPHONE = '' , containerno = '' , sealno = ''
, PRESETMODE = '' , CUSTOMSTDOCU = 'true' ,
CUSTOMSINSTRUCTION = '' , REMARKS = '' , vatid = '' ,
loadrequest = '' , lastvalidationstartdate = '' WHERE
id = 1351

The last query (2.) is not valid. All values are
written between single quotes, but some of them are
boolean or numeric.

Discussion

  • marco de toni
    marco de toni
    2005-04-21

    Logged In: YES
    user_id=417795

    I have the same problem with Oracle. It's a pity that I cannot
    use this tool.