| From: | Florent Guillaume <fg(at)nuxeo(dot)com> |
|---|---|
| To: | GEISINGER Marc - Contractor <Marc(dot)GEISINGER(at)external(dot)thalesgroup(dot)com> |
| Cc: | David Johnston <polobo(at)yahoo(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Bug in AbstracJdbc2Statement.replaceProcessing when using dollar quoting? |
| Date: | 2012-09-27 13:02:19 |
| Message-ID: | CAF-4BpPaaiZuHX=6Rjtksuhf0PJYHDiroVRV3Yn4dFOEJqkhSw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, Sep 26, 2012 at 5:07 PM, GEISINGER Marc - Contractor
<Marc(dot)GEISINGER(at)external(dot)thalesgroup(dot)com> wrote:
> Von: David Johnston [mailto:polobo(at)yahoo(dot)com]
>> Which is why my suggestion is possibly superior and at least simpler (thus less prone to bugs).
>> Once you find the non-conforming dollar-quote start tag in the query simply abort the JDBC specific code and return the query unmodified.
>
> Since $ in identifiers are postgres-only, there is no reason to try to be postgres-indepentend with SQL escape codes. I think your suggestion would be ok to handle dollar quotes.
Oracle is well known for its V$SESSION and other similar tables.
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
| From | Date | Subject | |
|---|---|---|---|
| Next Message | antthelimey | 2012-09-28 14:05:53 | "Select * " on 12-18M row table from remote machine thru JDBC - Performance nose-dives after 10M-ish records |
| Previous Message | Dave Cramer | 2012-09-27 11:49:07 | Re: isValid availability |