Bruce Momjian wrote:
Tom Lane wrote:
Steve Clark <[EMAIL PROTECTED]> writes:
I'm not sure I understand what you mean about TEXT being null-safe.
What are the issues, and why was
it supported for years and now abruptly changed.
It never was supported, we are simply plugging a hole that let you
create a text value that would be likely to malfunction in subsequent
use.
Seems we never documented that chr(0) is not supported. I have applied
the following doc patch to CVS HEAD and 8.3.X.
The NULL (0) character is not
allowed because text data types cannot reliably store such bytes.
"Reliably" is arguably misleading here.
cheers
andrew
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your Subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-patches
