| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: targetlist functions part 1 (was [HACKERS] targetlist |
| Date: | 2003-01-13 22:46:04 |
| Message-ID: | Pine.LNX.4.44.0301132253430.789-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Joe Conway writes:
> The short answer is we need a way to allow a "table function" to fire
> multiple times given one or more columns from a table as input.
Has there been an evaluation of the SQL standard and other databases how
this is handled? I can't believe we're operating in ground-breaking
territory here. What concerns me is that we're inserting table-generating
syntax elements into the select list, which is where they've never
belonged.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-01-13 22:46:28 | Re: \d type queries - why not views in system catalog?!? |
| Previous Message | Hannu Krosing | 2003-01-13 22:06:55 | Re: \d type queries - why not views in system catalog?!? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-01-13 22:46:44 | Re: Add UNIQUE and PRIMARY KEY to pg_get_constraintdef |
| Previous Message | Tom Lane | 2003-01-13 22:16:09 | Re: insert rule doesn't see id field |