| From: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
|---|---|
| To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, Joerg Hessdoerfer <Joerg(dot)Hessdoerfer(at)sea-gmbh(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bytea/Base64 encoders for libpq - interested? |
| Date: | 2001-08-29 02:22:22 |
| Message-ID: | 3.0.5.32.20010829102222.00853760@192.228.128.13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
At 11:55 AM 28-08-2001 +0200, Karel Zak wrote:
> What implement base64 PostgreSQL datetype that use externaly base64 and
>internaly same things as bytea. It prevent FE and parser problems with
Another point:
I have no problems with base64[1]. However I was thinking that it might be
far easier for the C/C++/Java (and other low level languages) bunch to do
hexadecimal. e.g. zero zero for null, zero A for line feed.
It expands things in the input/output stream, but it might be worth some
consideration. Simplicity, cpu usage etc.
Cheerio,
Link.
[1] OK, I can't convert base64 to ASCII mentally yet. But I don't think
that should really a factor.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2001-08-29 02:31:54 | cannot detect too many clients |
| Previous Message | Lincoln Yeoh | 2001-08-29 01:58:12 | Re: Bytea/Base64 encoders for libpq - interested? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2001-08-29 05:26:06 | RE: ADD CONSTRAINT UNIQUE patch |
| Previous Message | Lincoln Yeoh | 2001-08-29 01:58:12 | Re: Bytea/Base64 encoders for libpq - interested? |