| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
| Cc: | ljb <lbayuk(at)mindspring(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Re: Examples of using bytea type |
| Date: | 2001-07-20 16:05:54 |
| Message-ID: | 200107201605.f6KG5sK16315@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-07-20 16:15:20 | Re: bug in hash indexes??? |
| Previous Message | Bruce Momjian | 2001-07-20 16:03:01 | Re: RPM source files should be in CVS (was Re: psql -l) |