Re: targetlist functions part 1 (was [HACKERS] targetlist

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Joe Conway <mail(at)joeconway(dot)com>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: targetlist functions part 1 (was [HACKERS] targetlist
Date: 2003-01-13 22:50:10
Message-ID: 6801.1042498210@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> I can't believe we're operating in ground-breaking
> territory here.

We're not. This functionality has always been in Postgres, right back
to the PostQUEL days. Joe is trying to clean it up to the point where
it has explainable, defensible semantics. But he's not adding something
that wasn't there before.

> What concerns me is that we're inserting table-generating
> syntax elements into the select list, which is where they've never
> belonged.

Do you see another way to pass non-constant arguments to the
table-generating function?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-01-13 22:57:31 Re: \d type queries - why not views in system catalog?!?
Previous Message Bruce Momjian 2003-01-13 22:49:54 Re: PostgreSQL site, put up or shut up?

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-01-14 00:29:07 Re: fix broken regression tests
Previous Message Peter Eisentraut 2003-01-13 22:46:44 Re: Add UNIQUE and PRIMARY KEY to pg_get_constraintdef