Re: Simplifying unknown-literal handling

From: Andrew - Supernews <andrew+nonews(at)supernews(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Simplifying unknown-literal handling
Date: 2005-05-29 20:10:23
Message-ID: slrnd9k8df.1d3v.andrew+nonews@trinity.supernews.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2005-05-29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew - Supernews <andrew+nonews(at)supernews(dot)com> writes:
>> Are there any cases where UNKNOWN can be received from the frontend as
>> a binary value? I suspect there are.
>
> Sure, but that's transparent because we have binary I/O converters.
> You will have trouble if you try to inject an embedded zero that way,
> but the end result will look about the same as when you try to inject
> an embedded zero now: the data after the zero will be dropped on readout.

What happens if you send an UNKNOWN from the frontend as binary, and then
when the desired type is figured out, it turns out to be a bytea? It's
obviously not acceptable then to truncate after a zero byte.

--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-05-29 21:43:39 Re: Simplifying unknown-literal handling
Previous Message Tom Lane 2005-05-29 19:13:58 Re: Simplifying unknown-literal handling