From: | Howard Yeh <hayeah(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Byte Escape Syntax |
Date: | 2010-04-15 18:22:26 |
Message-ID: | n2xab5a379d1004151122r61267c5ar5750e1808f7bc507@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 15, 2010 at 10:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
is this something that could be set at runtime? Does it apply to the
whole database server?
Thanks!
>
>> 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 19:24:49 | Re: solaris tarballs and pl/java |
Previous Message | Jorge Arevalo | 2010-04-15 18:16:08 | Re: Showing debug messages in my C function |