| 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 18:27:59 |
| Message-ID: | slrnd9k2df.1d3v.andrew+nonews@trinity.supernews.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2005-05-29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)surnet(dot)cl> writes:
>> On Sun, May 29, 2005 at 11:47:18AM -0400, Tom Lane wrote:
>>> Anyone see a reason not to change this?
>
>> Is there any way we use UNKNOWN to represent bytea literals?
>> Say, comparing a untyped literal to a bytea column?
>
> We use UNKNOWN to represent the raw string literal before we've
> figured out that we need to feed it to byteain. There aren't
> going to be any embedded nulls at that point, if that's what
> you are wondering.
Are there any cases where UNKNOWN can be received from the frontend as
a binary value? I suspect there are.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-29 19:10:32 | Re: Escape handling in COPY, strings, psql |
| Previous Message | Peter Eisentraut | 2005-05-29 18:00:19 | Re: Escape handling in COPY, strings, psql |