From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Florian Weimer <fweimer(at)bfk(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Making TEXT NUL-transparent |
Date: | 2011-11-24 09:21:21 |
Message-ID: | CAFj8pRDpQTDEofA43YsxHM_EgFeJBUm2aBrm4pYhEu9LcaQKMQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello
2011/11/24 Florian Weimer <fweimer(at)bfk(dot)de>:
> Occasionally, we get bitten by embedded NUL bytes in TEXT values. We
> take care of generating proper UTF-8, but this additional restriction
> sometimes slips by. It would be really helpful if PostgreSQL could
> store such TEXT fields as-is (at least if they are computed internally,
> or come from query parameters).
>
and why you don't use bytea ? Text should be correct literal.
Regards
Pavel Stehule
> I haven't even looked how difficult it would be to implement this. Do
> you think it's worth the trouble?
>
> --
> Florian Weimer <fweimer(at)bfk(dot)de>
> BFK edv-consulting GmbH http://www.bfk.de/
> Kriegsstraße 100 tel: +49-721-96201-1
> D-76133 Karlsruhe fax: +49-721-96201-99
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2011-11-24 09:24:09 | Re: [PATCH] PostgreSQL fails to build with 32bit MinGW-w64 |
Previous Message | Florian Weimer | 2011-11-24 09:06:43 | Making TEXT NUL-transparent |