Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5O0K6a86183 for ; Sat, 23 Jun 2001 20:20:06 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.10.1/8.10.1) id f5NE2jS03849; Sat, 23 Jun 2001 10:02:45 -0400 (EDT) From: Bruce Momjian Message-Id: <200106231402.f5NE2jS03849@candle.pha.pa.us> Subject: Re: Re: Re: binary data In-Reply-To: <4217.993224417@sss.pgh.pa.us> "from Tom Lane at Jun 22, 2001 11:40:17 am" To: Tom Lane Date: Sat, 23 Jun 2001 10:02:45 -0400 (EDT) CC: Karel Zak , Hugh Mandeville , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200106/392 X-Sequence-Number: 3689 > 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. bytea is binary compatible with text/varchar()/char(), right? It stores the same format. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026