| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Florian Weimer <fweimer(at)bfk(dot)de> |
| Cc: | Alexander Shulgin <ash(at)commandprompt(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Making TEXT NUL-transparent |
| Date: | 2011-11-24 13:40:30 |
| Message-ID: | CA+TgmoZ6SWbNgpJ=xKAoxh=H+Z1+eGGtZcV28oCuPL5nqt+0_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 24, 2011 at 4:54 AM, Florian Weimer <fweimer(at)bfk(dot)de> wrote:
> By the way, I refuse the notion that UTF-8 strings with embedded NULs
> are "broken". I can't recall any other system which enforces UTF-8
> well-formedness, but does not permit embedded NULs.
This seems like a key point. If UTF-8 allows embedded NULs, then a
text field supposedly encoded as UTF-8 ought to allow them, too.
However, our propensity to translate between text and cstring might
make this difficult to implement in practice.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Shulgin | 2011-11-24 13:43:11 | Re: Notes on implementing URI syntax for libpq |
| Previous Message | Robert Haas | 2011-11-24 13:35:36 | Re: Notes on implementing URI syntax for libpq |