Re: Prepared Statement is not parsed correctly
От | Kris Jurka |
---|---|
Тема | Re: Prepared Statement is not parsed correctly |
Дата | |
Msg-id | Pine.BSO.4.61.0602011358400.213@leary.csoft.net обсуждение исходный текст |
Ответ на | Prepared Statement is not parsed correctly ("Senden Kris" <Kris.Senden@realsoftwaregroup.com>) |
Список | pgsql-jdbc |
On Wed, 1 Feb 2006, Senden Kris wrote: > 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 > > 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. > Fixed in cvs for 8.0, 8.1, and HEAD. New 8.1 jars available here: http://www.ejurka.com/pgsql/jars/sk/ Kris Jurka
В списке pgsql-jdbc по дате отправления: