Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5MFeXa44029 for ; Fri, 22 Jun 2001 11:40:33 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f5MFeH304220; Fri, 22 Jun 2001 11:40:17 -0400 (EDT) To: Karel Zak cc: Hugh Mandeville , pgsql-sql@postgresql.org Subject: Re: Re: Re: binary data In-reply-to: <20010622173537.A14265@ara.zf.jcu.cz> References: <9gtovc$mnr$1@news.tht.net> <3791.993219752@sss.pgh.pa.us> <20010622173537.A14265@ara.zf.jcu.cz> Comments: In-reply-to Karel Zak message dated "Fri, 22 Jun 2001 17:35:37 +0200" Date: Fri, 22 Jun 2001 11:40:17 -0400 Message-ID: <4217.993224417@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/375 X-Sequence-Number: 3667 Karel Zak 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