BUG #15130: outer-join-escape syntax seems not to work with latest jdbc-driver

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: markus(dot)koch(at)community4you(dot)de
Subject: BUG #15130: outer-join-escape syntax seems not to work with latest jdbc-driver
Date: 2018-03-26 10:24:59
Message-ID: 152205989951.4535.13421588945663164374@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 15130
Logged by: Markus Koch
Email address: markus(dot)koch(at)community4you(dot)de
PostgreSQL version: 9.4.7
Operating system: SuSE Linux
Description:

We are using Crystal Report Java Reporting Component (JRC) to create
reports.

Crystal reports creates queries like this:
SELECT "CODE"."system_bez",
"FAHRZEUG"."fahrzeug_id", "FAHRZEUG"."hersteller", "FAHRZEUG"."x_inaktiv",

"G_PARTNER"."g_partner_id", "CODE"."code_table", "G_PARTNER"."name"
FROM {oj ("public"."fahrzeug" "FAHRZEUG" LEFT OUTER JOIN
"public"."g_partner"
"G_PARTNER" ON "FAHRZEUG"."g_partner_id"="G_PARTNER"."g_partner_id")
LEFT OUTER JOIN "public"."code" "CODE" ON
"FAHRZEUG"."obj_code_id"="CODE"."code_id"}
WHERE ("G_PARTNER"."g_partner_id"=1 AND "FAHRZEUG"."x_inaktiv"
IS NULL AND ("CODE"."code_table"='OBJ_TYP' AND
"CODE"."system_bez"='FAHRZEUG'))
ORDER BY "G_PARTNER"."g_partner_id"

According to this page:
https://jdbc.postgresql.org/documentation/head/outer-joins-escape.html
this syntax should still work but in fact it works only up to
postgresql-9.4.1211.jre7.jar.

If we replace the jdbc-driver postgresql-9.4.1212.jre7.jar or a newer
version we're getting this error: ERROR: syntax error at or near "{"

I think this is related to the postgres-jdbc-driver because this is the only
lib I have replaced.

Markus

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-03-26 12:14:38 Re: PostgreSQL crashes with SIGSEGV
Previous Message Tom Lane 2018-03-25 15:43:20 Re: BUG #15129: Problem with UNION/UNION ALL type setting when several NULL values before defining the proper type