From: | "Eugene E(dot)" <sad(at)bankir(dot)ru> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: have you feel anything when you read this ? |
Date: | 2006-03-20 12:44:26 |
Message-ID: | 441EA3AA.3080909@bankir.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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() ?
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleus Mantzios | 2006-03-20 13:06:11 | Re: have you feel anything when you read this ? |
Previous Message | Eugene E. | 2006-03-20 12:31:35 | Re: have you feel anything when you read this ? |