Kuba Ober (winnie(at)hoth(dot)amu(dot)edu(dot)pl) reports a bug with a severity of 3
The lower the number the more severe it is.
Subselects lack functionality
Subselects don't allow one to use tuple set operators like UNION, INTERSECT, EXCEPT. It forces one to select the results into a temp table.
It would be gr8 if single column subselects would allow themselves to be treated the same way as lists do as right-side arguments of IN operator.
This would allow e.g. much more powerful DELETE statement, like
DELETE FROM table WHERE id IN (SELECT ...)
Subselects cannot be used as arguments to aggregation functions - I presume this is very weird and not expected at all, but I had such an idea.
I don't know if it is expected behaviour (standards?), this should be explained in the docs (or am I searching in the wrong place?)
select (select id from table1 except select table1.id where expression) as id;
(assuming that subselect would result just one tuple)
No file was uploaded with this report
pgsql-bugs by date
|Next:||From: Lamar Owen||Date: 2000-09-28 22:20:52|
|Subject: Re: Subselects lack functionality|
|Previous:||From: pgsql-bugs||Date: 2000-09-28 19:08:44|
|Subject: very poorly optimised query|