Re: [HACKERS] subselects coding started - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] subselects coding started
Date
Msg-id 199801171600.LAA22977@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] subselects coding started  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
List pgsql-hackers
>
> Bruce Momjian wrote:
>
> > OK, I have created the SubLink structure with supporting routines, and
> > have added code to create the SubLink structures in the parser, and have
> > added Query->hasSubLink.
> >
> > I changed gram.y to support:
> >
> >         (x,y,z) OP (subselect)
> >
> > where OP is any operator.  Is that right, or are we doing only certain
> > ones, and of so, do we limit it in the parser?
>
> Seems like we would want to pass most operators and expressions through
> gram.y, and then call elog() in either the transformation or in the
> optimizer if it is an operator which can't be supported.
>

That's what I thought.

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: Peter T Mount
Date:
Subject: Re: [HACKERS] PSQL man page patch
Next
From: darrenk@insightdist.com (Darren King)
Date:
Subject: Group By, NULL values and inconsistent behaviour.