Oleg Broytmann wrote:
> VIEW on 6.4.2 ignores DISTINCT. Is it a bug? known?
It's a known missing feature (not a bug - more like a design
DISTINCT is implemented as a unique sort step taken over the
final result of a query. Views are implemented via the query
rewrite rule system. If now someone would define a DISTINCT
view and selects a join of it with another table, the rewrite
system cannot tell the planner that only the scan's resulting
from the view should be sorted unique. It could only tell
that the entire result should be DISTINCT - what's wrong - so
I left it out.
I'm planning to implement some kind of subquery rangetable
entries someday. At that time, all these problems (DISTINCT,
GROUP BY, ORDER BY) of views will disappear.
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
pgsql-hackers by date
|Next:||From: Zeugswetter Andreas IZ5||Date: 1999-04-26 07:00:46|
|Subject: AW: [HACKERS] Re: light dawns: serious bug in FE/BE protocol handling |
|Previous:||From: Vadim Mikheev||Date: 1999-04-26 06:57:03|
|Subject: Re: [HACKERS] A patch for FATAL 1:btree: BTP_CHAIN flag was expected|