Skip site navigation (1) Skip section navigation (2)

Re: PQescapeString handling of \0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
Cc: greg(at)turnstep(dot)com, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PQescapeString handling of \0
Date: 2003-10-03 16:02:03
Message-ID: 26244.1065196923@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
"Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:
> On Fri, Oct 03, 2003 at 11:31:02AM -0400, Tom Lane wrote:
>> So essentially PQescapeString is going to become like strncpy --- stop
>> at either \0 or the given count.

> I've no idea whether this makes sense, but as a matter of style, shouldn't
> strings containing '\0's be escaped as binary strings anyway?  And if we're
> going to see multibyte encodings growing in popularity (lots of zeroes and
> "high" byte values), perhaps PQescapeString should even be deprecated?

I think you might be confusing PQescapeString (intended for text) with
PQescapeBytea (intended for binary data).  We do not support any text
encodings that require embedded zeroes, and are unlikely to do so
anytime soon.  (Had anyone suggested this as a design goal when we were
doing the recent FE/BE protocol redesign, perhaps the protocol wouldn't
still rely on null-terminated strings.  But no one did and it's too late
now.)

			regards, tom lane

In response to

Responses

pgsql-interfaces by date

Next:From: Jeroen T. VermeulenDate: 2003-10-03 16:05:27
Subject: Re: PQescapeString handling of \0
Previous:From: Jeroen T. VermeulenDate: 2003-10-03 15:51:02
Subject: Re: PQescapeString handling of \0

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group