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

From Thomas G. Lockhart
Subject Re: [HACKERS] subselects coding started
Date
Msg-id 34C044D5.C21FE707@alumni.caltech.edu
Whole thread Raw
In response to subselects coding started  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] subselects coding started  (Bruce Momjian <maillist@candle.pha.pa.us>)
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.

                                           - Tom


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: subselects coding started
Next
From: teunis
Date:
Subject: Re: [HACKERS] Re: [QUESTIONS] Arrays (inserting and removing)