From: Tom Lane <tgl@sss.pgh.pa.us>
To: Karel Zak <zakkr@zf.jcu.cz>
Cc: Hugh Mandeville <hughmandeville@hotmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Re: Re: binary data
Date: Fri, 22 Jun 2001 11:40:17 -0400
Message-ID: <4217.993224417@sss.pgh.pa.us> (raw)
In-Reply-To: <20010622173537.A14265@ara.zf.jcu.cz>
References: <Pine.BSO.4.10.10106201342060.20262-100000@spider.pilosoft.com>
<9gtovc$mnr$1@news.tht.net>
<3791.993219752@sss.pgh.pa.us>
<20010622173537.A14265@ara.zf.jcu.cz>
Karel Zak <zakkr@zf.jcu.cz> writes:
> On Fri, Jun 22, 2001 at 10:22:32AM -0400, Tom Lane wrote:
>> He did say the rules for escaping things are tricky ;-).
> And what use some better encoding if you have a lot of binary chars
> in data. For example base64, that code 2 chars to 3 instead \\000
> that encode 1 char to 4.
Yeah, it's pretty messy. Perhaps we could offer a couple of conversion
functions that convert bytea to or from base64 or other popular
encodings. bytea is pretty impoverished --- it hasn't received the
attention it deserves.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, zakkr@zf.jcu.cz, hughmandeville@hotmail.com
Subject: Re: Re: Re: binary data
In-Reply-To: <4217.993224417@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox