Re: [HACKERS] subselects coding started
| От | Thomas G. Lockhart |
|---|---|
| Тема | Re: [HACKERS] subselects coding started |
| Дата | |
| Msg-id | 34C044D5.C21FE707@alumni.caltech.edu обсуждение исходный текст |
| Ответ на | subselects coding started (Bruce Momjian <maillist@candle.pha.pa.us>) |
| Ответы |
Re: [HACKERS] subselects coding started
|
| Список | 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 по дате отправления: