| From: | Marko Kreen <marko(at)l-t(dot)ee> |
|---|---|
| To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] by request: base64 for bytea |
| Date: | 2001-06-23 13:43:33 |
| Message-ID: | 20010623154333.A22027@l-t.ee |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-06-23 13:48:18 | Re: [PATCH] by request: base64 for bytea |
| Previous Message | Alex Pilosov | 2001-06-23 12:42:46 | Re: [PATCH] by request: base64 for bytea |