Re: [GENERAL] NAB : insert into select distinct => when used on null, distinct causes loss of type knowledge Frank van Vugt Tue, 24 Aug 2004 14:39:43 -0700 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. ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org Previous message View by thread View by date Next message [GENERAL] NAB : insert into <table> select distinct &... Frank van Vugt Re: [GENERAL] NAB : insert into <table> select d... Tom Lane Frank van Vugt Reply via email to Search the site The Mail Archive home pgsql-general - all messages pgsql-general - about the list Expand Previous message Next message The Mail Archive home Add your mailing list FAQ Support Privacy 200408242337.02757.ftm.van.vugt@foxi.nl

[Frank van Vugt]

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.


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org