| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Joe Conway <joseph(dot)conway(at)home(dot)com>, Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, Joerg Hessdoerfer <Joerg(dot)Hessdoerfer(at)sea-gmbh(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bytea/Base64 encoders for libpq - interested? |
| Date: | 2001-09-04 17:33:26 |
| Message-ID: | 27436.999624806@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Let me ask a bigger question. We have the length of the text string in
> the varlena header. Are we concerned about backend code not handling
> NULL in text fields, or frontend code returning strings with embedded
> nulls?
The former.
> I see problems in the text() functions for nulls, but is such a
> limitation required for text types?
Unless you want to re-implement strcoll() and friends from scratch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-09-04 17:34:37 | Re: Bytea/Base64 encoders for libpq - interested? |
| Previous Message | Bruce Momjian | 2001-09-04 17:30:54 | Re: Escaping strings for inclusion into SQL queries |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-09-04 17:34:37 | Re: Bytea/Base64 encoders for libpq - interested? |
| Previous Message | Dave Cramer | 2001-09-04 17:20:41 | Re: Read transactions don't work on 7.0.x db's 2nd patch |