| From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Re: Examples of using bytea type |
| Date: | 2001-07-20 16:40:31 |
| Message-ID: | Pine.BSO.4.10.10107201239520.29964-100000@spider.pilosoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 20 Jul 2001, Bruce Momjian wrote:
> > Bytea IS documented in 7.2-devel and is definitely not going away. Major
> > benefit of bytea over base64/whatever encoding is storage space. Need to
> > escape/unescape input data depends on your frontend client. Perl DBD::Pg
> > will do it transparently without needing to do \\ escapes.
> >
> > In 7.2, there will also be functions base64_encode/base64_decode for bytea
> > types. In 7.1, they exist under contrib/pg_crypto
>
> Do they need to be removed from 7.2 /contrib? Please tell me how.
Nono. Ones in /contrib are much more than encoding, its whole crypto
setup. Ones in core are slightly modified versions of them which only take
care of encode/decode.
-alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-07-20 16:41:22 | Re: How Postgresql Compares For Query And Load Operations |
| Previous Message | Tom Lane | 2001-07-20 16:35:34 | Re: RPM source files should be in CVS (was Re: psql -l) |