From: | Nis Jorgensen <nis(at)superlativ(dot)dk> |
---|---|
To: | Nis Jorgensen <nis(at)superlativ(dot)dk>, Agent M <agentm(at)themactionfaction(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Fabian Pascal and RDBMS deficiencies in fully implementing |
Date: | 2006-06-09 14:07:17 |
Message-ID: | 44898095.6070204@superlativ.dk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Roman Neuhauser wrote:
> # nis(at)superlativ(dot)dk / 2006-06-09 10:12:21 +0200:
>> Agent M wrote:
>>> If you don't use NULL, then you don't
>>> come across 3-valued logic--problem solved.
>> So was does "SELECT sum(1) FROM dual WHERE false" return?
>
> You stripped this:
>
>>> Some Tutorial D notions really make sense; I would love to be able
>>> to rely on every function returning a relation.
Yes. I didn't see its relevance to the claim that "if you don't use
null, you will not come across 3-valued logic". My point being that you
need to make sure that your queries don't generate them behind your back
either.
> So your query would prolly return a table with one (INT) column,
> but no rows.
Well, if you are not bound by the SQL standard and its mistakes, the
"obvious" return value would be one row, one column, containing 0.
/Nis
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-09 14:26:39 | Re: How to set the global OID counter? COPY WITH OIDS does not set global OID counter? |
Previous Message | Alvaro Herrera | 2006-06-09 14:00:15 | Re: How to set the global OID counter? COPY WITH OIDS does not set global OID counter? |
From | Date | Subject | |
---|---|---|---|
Next Message | Milen Kulev | 2006-06-09 14:08:54 | Re: PG 8.2 |
Previous Message | Tom Lane | 2006-06-09 14:00:20 | Re: That EXPLAIN ANALYZE patch still needs work |