From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Howard Yeh <hayeah(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Byte Escape Syntax |
Date: | 2010-04-15 17:45:55 |
Message-ID: | 4830.1271353555@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Howard Yeh <hayeah(at)gmail(dot)com> writes:
> Is Postgres's byte escape syntax something that could be set by the client?
Well, indirectly --- it's affected by the standard_conforming_strings
setting.
> I am running into a strange problem when I access postgres try two
> different Ruby ORM's. I am guessing that one of them is doing
> something funny to the client connections.
> Looking at the Ruby C-driver, it's calling PQescapeBytea rather then
> PQescapeByteaConn. And tracing PQescapeBytea, sometimes it escapes '\'
> as '\\', as describe in the manual, sometimes it doesn't do that
> escape. But it always escape the single quote character ' . All the
> connections are using UTF-8 encoding.
It would be a real good idea to fix that driver to use PQescapeByteaConn.
There are no supported releases of Postgres that don't have that
function.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2010-04-15 18:03:07 | Re: solaris tarballs and pl/java |
Previous Message | Howard Yeh | 2010-04-15 17:30:15 | Byte Escape Syntax |