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

Re: Upcoming events

From: "Joe Conway" <joseph(dot)conway(at)home(dot)com>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Upcoming events
Date: 2001-08-28 02:03:59
Message-ID: 010701c12f65$b3eb01d0$0705a8c0@jecw2k1 (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> Does anyone else have work that they're trying to finish up before
> we go beta?

Well, I did have a question that got lost in the details of the recent bytea
discussion. Specifically it was this: is there a good reason that byteaout
octal escapes all non-printable characters?

ISTM that if you are using bytea, it's because you need to store and
manipulate binary data, and therefore it ought to be the client's
responsibility to do any required escaping of the returned results. In the
work I'm doing with bytea presently, I either have to unescape it on the
client side, or use a binary cursor (and some app environments, like PHP,
don't currently give me the option of a binary cursor). Not that big of a
deal, but it doesn't seem right, and as you've seen by recent discussions it
confuses people.

The only reason I can think of for this behavior is that it makes the
results displayable in psql -- but again, I'd expect psql to deal with that,
not the backend.


-- Joe

In response to


pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2001-08-28 02:09:45
Subject: RE: Upcoming events
Previous:From: Thomas LockhartDate: 2001-08-28 02:02:16
Subject: Re: Locale by default?

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