Re: BUG #2189: Prepared Statement is not parsed correctly - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #2189: Prepared Statement is not parsed correctly
Date
Msg-id 200601220244.k0M2iBm07507@candle.pha.pa.us
Whole thread Raw
In response to BUG #2189: Prepared Statement is not parsed correctly  ("Kris Senden" <kris.senden@realsoftware.be>)
List pgsql-bugs
This is not the place to report jdbc problems.  The jdbc project has its
own mailing lists.

---------------------------------------------------------------------------

Kris Senden wrote:
>
> The following bug has been logged online:
>
> Bug reference:      2189
> Logged by:          Kris Senden
> Email address:      kris.senden@realsoftware.be
> PostgreSQL version: 8.0.2
> Operating system:   Windows XP/2K/2003
> Description:        Prepared Statement is not parsed correctly
> Details:
>
> Recently we discovered a defect in the jdbc driver of PostgreSQL. It is
> detected in version 8.1dev-401 and also found in all later versions. The
> problem is that we had a faulty SQL statement in our code that was partly
> executed by the jdbc-driver without any warning or error log.
> The statement is SELECT * FROM POSTransaction WHERE DatTransEnd = (SELECT
> MAX(DatTransEnd) FROM POSTransaction WHERE IdtCheckout = 9 AND FlgTraining =
> ?) AND IdtCheckout = 9 AND FlgTraining = ?) ORDER BY HouTransEnd DESC. As
> you can see this statement contains 1 closing bracket ('(') too much.
> However while debugging the driver I saw that the problem is caused in
> method AbstractJdbc2Statement.parseSql(String, int, StringBuffer, boolean)
> throws SQLException. In that method a counter is activated which holds the
> number of open brackets. Each time it encounters a ( it adds one and each
> time it encounters a ) it substracts one. When the counter's value is less
> than zero, the parsings stops.
> In our case, this resulted that our sql statement was shortened to SELECT *
> FROM POSTransaction WHERE DatTransEnd = (SELECT MAX(DatTransEnd) FROM
> POSTransaction WHERE IdtCheckout = 9 AND FlgTraining = ?) AND IdtCheckout =
> 9 AND FlgTraining = ?
> When executing the same query in  pgAdmin III Query, I got a syntax error :
> ERROR:  syntax error at or near ")" at character 136. I would expected to
> have the same syntax error using the prepared statement.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-bugs by date:

Previous
From: Giles Morant
Date:
Subject: Re: BUG #2177: (minor:) pgsql: Trailing semicolon on \d treated as argument
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #2190: ODBC SQLPrimaryKeys PK_NAME missing info