Skip site navigation (1) Skip section navigation (2)

Re: Values list-of-targetlists patch for comments (was Re:

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, 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:
Date: 2006-08-04 20:35:09
Message-ID: 1154723709.2495.14.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackerspgsql-patches
On Thu, 2006-08-03 at 10:58 -0400, Tom Lane wrote:
> 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.

The DB2 manual does exactly that and is not any clearer as a result,
even if it is fully normalised.

If we did that we'd need to emphasise that VALUES is more of a clause
than a new command.

-- 
  Simon Riggs
  EnterpriseDB          http://www.enterprisedb.com


In response to

pgsql-docs by date

Next:From: Andrzej B.J.SchulzDate: 2006-08-09 05:23:25
Subject: unsubscribe
Previous:From: Peter EisentrautDate: 2006-08-04 07:02:09
Subject: Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]

pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-08-04 20:38:04
Subject: Re: WIP archive_timeout patch
Previous:From: David FetterDate: 2006-08-04 20:32:14
Subject: Re: 8.2 features status

pgsql-patches by date

Next:From: Simon RiggsDate: 2006-08-04 20:38:04
Subject: Re: WIP archive_timeout patch
Previous:From: Bruce MomjianDate: 2006-08-04 19:42:02
Subject: Re: PGStatement#setPrepareThreshold

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group