Re: [PATCH] by request: base64 for bytea

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Marko Kreen <marko(at)l-t(dot)ee>
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-24 02:41:41
Message-ID: 200106240241.f5O2ffB23109@candle.pha.pa.us
Views: Raw Message | Whole Thread | 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...

Sorry, backed out bytea binary compatibility code. Tom says it will not
work.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-06-24 02:46:09 Re: [PATCH] Re: Setuid functions
Previous Message Bruce Momjian 2001-06-24 02:37:29 Re: [PATCH] by request: base64 for bytea