Message-ID: <441EA3AA.3080909@bankir.ru>
Date: Mon, 20 Mar 2006 15:44:26 +0300
From: "Eugene E." <sad@bankir.ru>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050517)
MIME-Version: 1.0
To: Alvaro Herrera <alvherre@commandprompt.com>
CC: Achilleus Mantzios <achill@matrix.gatewaynet.com>,
	Peter Eisentraut <peter_e@gmx.net>, pgsql-sql@postgresql.org
Subject: Re: have you feel anything when you read this ?
References: <200603201251.11255.peter_e@gmx.net>
	<Pine.LNX.4.44.0603201504250.22800-100000@matrix.gatewaynet.com>
	<20060320121354.GA12564@surnet.cl> <441E9DEC.2070805@bankir.ru>
	<20060320122749.GC12564@surnet.cl>
In-Reply-To: <20060320122749.GC12564@surnet.cl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Alvaro Herrera wrote:
> Eugene E. wrote:
> 
>>Alvaro Herrera wrote:
> 
> 
>>>text is not bytea.
>>
>>source says:
>>
>>typedef text varlena;
>>typedef bytea varlena;
> 
> 
> This means that as far as the C type system is concerned, both bytea and
> text are treated as "struct varlena".  It doesn't mean that they are
> processed by the same input/output functions, which they aren't.
> 
> NUL bytes are preserved in bytea, and used as terminators in text.  I
> don't find this surprising at all, do you?

I do found surprising it.
since both (text and bytea) I/O functions has CSTRING arguments and 
resut type. - this only means a user should perform some unescaping on 
the bytea value he got. THE SAME THING he should do with a string value 
if he decide to use type text and to escape NUL-bytes before input.
then what a difference bitween those types except strlen() ?