Обсуждение: Re: [HACKERS] create view as select distinct (fwd)

Поиск
Список
Период
Сортировка

Re: [HACKERS] create view as select distinct (fwd)

От
jwieck@debis.com (Jan Wieck)
Дата:
Oleg Broytmann wrote:

>
> Hello!
>
>    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
    fault).

    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.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #

Re: [HACKERS] create view as select distinct (fwd)

От
Bruce Momjian
Дата:
Perhaps we should issue an error message if this is attempted until we
get it working?


> Oleg Broytmann wrote:
> 
> >
> > Hello!
> >
> >    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
>     fault).
> 
>     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.
> 
> 
> Jan
> 
> --
> 
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me.                                  #
> #======================================== jwieck@debis.com (Jan Wieck) #
> 
> 
> 
> 


--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026