Skip site navigation (1) Skip section navigation (2)

Re: Making TEXT NUL-transparent

From: Florian Weimer <fweimer(at)bfk(dot)de>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Making TEXT NUL-transparent
Date: 2011-11-24 09:27:51
Message-ID: 82d3chswdk.fsf@mid.bfk.de (view raw or flat)
Thread:
Lists: pgsql-hackers
* Pavel Stehule:

> 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.

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                <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

In response to

Responses

pgsql-hackers by date

Next:From: Alexander ShulginDate: 2011-11-24 09:35:02
Subject: Re: Making TEXT NUL-transparent
Previous:From: Boszormenyi ZoltanDate: 2011-11-24 09:24:09
Subject: Re: [PATCH] PostgreSQL fails to build with 32bit MinGW-w64

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group