Re: [HACKERS] subselects coding started

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] subselects coding started
Date: 1998-01-17 16:00:25
Message-ID: 199801171600.LAA22977@candle.pha.pa.us
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.
>

That's what I thought.

--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren King 1998-01-17 21:27:26 Group By, NULL values and inconsistent behaviour.
Previous Message Peter T Mount 1998-01-17 14:26:31 Re: [HACKERS] PSQL man page patch