Re: [PATCH] by request: base64 for bytea - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: [PATCH] by request: base64 for bytea
Date
Msg-id 20010623154333.A22027@l-t.ee
Whole thread Raw
In response to Re: [PATCH] by request: base64 for bytea  (Alex Pilosov <alex@pilosoft.com>)
Responses Re: [PATCH] by request: base64 for bytea  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [PATCH] by request: base64 for bytea  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [PATCH] by request: base64 for bytea  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Jun 23, 2001 at 08:42:46AM -0400, Alex Pilosov wrote:
> On Sat, 23 Jun 2001, Marko Kreen wrote:
> > 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.
> I think encode/decode should be part of core, as they are basic functions
> to manipulate bytea data...

Ok, I think I look into it.  I am anyway preparing a big update
to pgcrypto.

Question to -hackers: currently there is not possible to cast
bytea to text and vice-versa.  Is this intentional or bug?

It is weird because internal representation is exactly the same.
As I want my funtions to operate on both, do I need to create
separate funtion entries to every combination of parameters?
It gets crazy on encrypt_iv(data, key, iv, type) which has 3
parameters that can be both bytea or text...


-- 
marko



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Re: Setuid functions
Next
From: Marko Kreen
Date:
Subject: Re: [PATCH] by request: base64 for bytea