| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] subselects coding started |
| Date: | 1998-01-17 05:42:45 |
| Message-ID: | 34C044D5.C21FE707@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | teunis | 1998-01-17 06:56:27 | Re: [HACKERS] Re: [QUESTIONS] Arrays (inserting and removing) |
| Previous Message | Bruce Momjian | 1998-01-17 05:00:50 | subselects coding started |