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

Re: Making TEXT NUL-transparent

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alexander Shulgin <ash(at)commandprompt(dot)com>
Cc: Florian Weimer <fweimer(at)bfk(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making TEXT NUL-transparent
Date: 2011-11-24 11:38:17
Message-ID: CAFj8pRDkviY61oBujrEd1a20g3wntQv+b5ThM7YJnZu--4xRtw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2011/11/24 Alexander Shulgin <ash(at)commandprompt(dot)com>:
>
> Excerpts from Florian Weimer's message of Thu Nov 24 12:59:09 +0200 2011:
>>
>> > I have a different question. What is reason for embedded NULs inside
>> > strings?
>>
>> The source system does not enforce that constraint, so from time to
>> time, such data slips through.  I don't know why it's there in the first
>> place, and I have no control over the original data source.  Usually,
>> it's okay to silently strip NUL bytes; it's just a bit awkward.
>

the source should be buggy application that has broken replace or
concat of strings.

Pavel

> Strip?  Like this: "loss\0less" => "lossless"?  That would be awkward for sure.
>

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-11-24 11:57:17
Subject: Re: Notes on implementing URI syntax for libpq
Previous:From: Alexander ShulginDate: 2011-11-24 11:32:17
Subject: Re: Making TEXT NUL-transparent

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