| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | "raf(at)raf(dot)org" <raf(at)raf(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Inconsistent compilation error |
| Date: | 2018-04-19 12:13:15 |
| Message-ID: | CAKFQuwbr+uqkZM56DO_2Le6tAPPU6qGC-9Qx10WntndEwFxPfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday, April 18, 2018, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
>
> Hmm, wonder if there is an oops in the below:
>
> http://www.pygresql.org/contents/changelog.html
>
> Version 5.0 (2016-03-20)
> Changes in the DB-API 2 module (pgdb):
> "SQL commands are always handled as if they include parameters, i.e.
> literal percent signs must always be doubled. This consistent behavior is
> necessary for using pgdb with wrappers like SQLAlchemy."
I'd hope not, as far as the driver is concerned the percent signs are text
content. It's plpgsql that is interpreting them directly in the server.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akshay Ballarpure | 2018-04-19 12:56:38 | Re: pg_upgrade help |
| Previous Message | Fabio Pardi | 2018-04-19 10:14:01 | Re: pg_upgrade help |