* Pavel Stehule:
> Hello
>
> 2011/11/24 Florian Weimer <fwei...@bfk.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.
It's actually UTF-8 text, and some PostgreSQL functions are only
available for TEXT, but not BYTEA, e.g.:
bfk_int=> SELECT '\x006500'::bytea ~ 'A';
ERROR: operator does not exist: bytea ~ unknown
LINE 1: SELECT '\x006500'::bytea ~ 'A';
^
HINT: No operator matches the given name and argument type(s). You might need
to add explicit type casts.
--
Florian Weimer <fwei...@bfk.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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
