Re: NAB : insert into <table> select distinct <fields> => when used on null, distinct causes loss of type knowledge

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: NAB : insert into <table> select distinct <fields> => when used on null, distinct causes loss of type knowledge
Date: 2004-08-24 21:37:02
Message-ID: 200408242337.02757.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Tom,

> No, because it never had any: NULL is typeless (type UNKNOWN, to the
> parser). But to do a DISTINCT, the parser has to assign datatypes to all the
> columns (to determine the comparison rules). The default assumption for an
> UNKNOWN constant is type TEXT.

I grok, thanks for the quick reply.

--
Best,

Frank.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Donald 2004-08-24 22:01:42 Re: Gentoo for production DB server?
Previous Message Christine Desmuke 2004-08-24 21:33:47 Gentoo for production DB server?