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

Re: Making TEXT NUL-transparent

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Florian Weimer <fweimer(at)bfk(dot)de>
Cc: Alexander Shulgin <ash(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making TEXT NUL-transparent
Date: 2011-11-24 10:20:01
Message-ID: CAFj8pRDX2mUoqhQex2Mi3RA7gJhim3dvffYM79bgMChRxCyk3Q@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2011/11/24 Florian Weimer <fweimer(at)bfk(dot)de>:
> * Alexander Shulgin:
>
>>> 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
>>
>> And how will those TEXT functions behave on a value with an embedded
>> NUL?
>
> They need to be audited and fixed if necessary.  I'm not saying that
> this would be a trivial change.
>
>> Or is it not only about being able to *store* NULs in a text field?
>
> No, the entire core should be NUL-transparent.
>
> 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.
>

I have a different question. What is reason for embedded NULs inside strings?

Regards

Pavel Stehule

> --
> 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: Florian WeimerDate: 2011-11-24 10:59:09
Subject: Re: Making TEXT NUL-transparent
Previous:From: Florian WeimerDate: 2011-11-24 09:54:09
Subject: Re: Making TEXT NUL-transparent

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