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

Re: PQescapeString handling of \0

From: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: greg(at)turnstep(dot)com, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PQescapeString handling of \0
Date: 2003-10-03 15:51:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
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?


In response to


pgsql-interfaces by date

Next:From: Tom LaneDate: 2003-10-03 16:02:03
Subject: Re: PQescapeString handling of \0
Previous:From: Tom LaneDate: 2003-10-03 15:31:02
Subject: Re: PQescapeString handling of \0

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