On Fri, 4 Aug 2006, Peter Eisentraut wrote:
> Gavin Sherry wrote:
> > What do we want to do about documenting:
> >
> > regression=# values(1);
>
> Out of curiosity, according to what theory should that be allowed?
I asked this too. Tom pointed this out (I'd gi
On Thu, 3 Aug 2006, Peter Eisentraut wrote:
> Tom Lane wrote:
> > Should we give VALUES its own reference page? That doesn't quite
> > seem helpful either. cc'ing to pgsql-docs for ideas.
>
> This is probably the sort of thing that should be explained part II "The
> SQL Language". In particular
On Fri, 4 Aug 2006, Michael Glaesemann wrote:
> On Aug 3, 2006, at 23:58 , Tom Lane wrote:
>
>
> > Should we give VALUES its own reference page? That doesn't quite
> > seem helpful either.
> >
>
> I think we should go for a separate reference page, as VALUES appears
> to be expanding quite a bit.
On Thu, 3 Aug 2006, Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> 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
On Thu, 3 Aug 2006, Joe Conway wrote:
> Peter Eisentraut wrote:
> > Tom Lane wrote:
> >
> >>Should we give VALUES its own reference page? That doesn't quite
> >>seem helpful either. cc'ing to pgsql-docs for ideas.
> >
> > This is probably the sort of thing that should be explained part II "The
>
Though it was published some time ago, I only just came across this
article:
http://www.suite101.com/article.cfm/oracle/115560
The comparison criteria is primative but PostgreSQL does well. I must say,
I was thrown by this comment:
"That web site includes a very good installation document. Howev
On Tue, 21 Dec 2004, Harry wrote:
> What is the preferred format if writing postgresql documentation?
>
> Is plain text OK?
They're marked up in docbook. Check out cvs
(http://developer.postgresql.org/docs/postgres/cvs.html. The document
source is in doc/src/sgml/.
Thanks,
Gavin
--
