From: | Marko Kreen <marko(at)l-t(dot)ee> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Alex Pilosov <alex(at)pilosoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] by request: base64 for bytea |
Date: | 2001-06-23 11:11:34 |
Message-ID: | 20010623131134.A21486@l-t.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 22, 2001 at 09:55:46PM -0400, Bruce Momjian wrote:
> Your patch has been added to the PostgreSQL unapplied patches list at:
> > Attached is a patch (including documentation this time :) containing two
> > functions, base64_encode(bytea) and base64_decode(text) with obvious
> > functionality.
Btw, there are functions in form encode(data, 'base64'),
decode(data, 'base64') in contrib/pgcrypto. They do also
encode(data, 'hex'). In the future I need to do probably
encode(data, 'pgp-armor') too...
I agree those functionality should be in core code, and if
the Alex ones get there, maybe he could use same interface?
Or I can extract it out from pgcrypto and submit to core ;)
I simply had not a need for it because I used those with
pgcrypto, but Alex seems to hint that there would be bit of
interest otherwise too.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Pilosov | 2001-06-23 12:42:46 | Re: [PATCH] by request: base64 for bytea |
Previous Message | Tom Lane | 2001-06-23 04:53:47 | Re: Multiple Indexing, performance impact |