| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, pgsql-patches(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Values list-of-targetlists patch for comments (was Re: [PATCHES] |
| Date: | 2006-08-03 14:58:10 |
| Message-ID: | 18685.1154617090@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers pgsql-patches |
Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> Docs and regression tests attached.
I've applied the regression tests (with a few additions), but I'm
feeling dissatisfied with this approach to documenting VALUES.
It seems to be mostly missing the point about VALUES being usable
whereever SELECT is. I'm not at all sure what I'd do instead though.
Should we give VALUES its own reference page? That doesn't quite
seem helpful either. cc'ing to pgsql-docs for ideas.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Glaesemann | 2006-08-03 15:56:20 | Re: Values list-of-targetlists patch for comments (was Re: [PATCHES] |
| Previous Message | Tom Lane | 2006-08-03 12:48:57 | Re: VALUES clause memory optimization (was: Values list-of-targetlists patch...) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-03 15:04:44 | Re: pg_terminate_backend |
| Previous Message | Michael Meskes | 2006-08-03 14:54:35 | Re: ecpg test suite |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-03 15:22:58 | Re: GIN vs. statistics collector |
| Previous Message | Tom Lane | 2006-08-03 12:48:57 | Re: VALUES clause memory optimization (was: Values list-of-targetlists patch...) |