pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Roberto Mello <rmello@cc.usu.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: lockhart@fourpalms.org, Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-docs@postgresql.org
Subject: Re: Re: [HACKERS] Re: 7.1 docs
Date: Sun, 25 Mar 2001 09:23:10 -0700
Message-ID: <20010325092310.A8329@cc.usu.edu> (raw)
In-Reply-To: <22991.985451522@sss.pgh.pa.us>
References: <Pine.LNX.4.30.0103241339310.2319-100000@peter.localdomain>
	<22991.985451522@sss.pgh.pa.us>

On Sat, Mar 24, 2001 at 11:32:02AM -0500, Tom Lane wrote:
> 
> A "page per function" approach is clearly overkill for the vast majority
> of our functions.  I think that's not unrelated to the fact that no one's
> ever bothered to prepare such documentation ;-)

	Agreed.
 
> On the other hand, the existing layout of the User's Guide encourages a
> "line per function" approach, which is insufficient for at least some
> functions.  We've worked around that by adding paragraphs below the main
> table on each page, but that seems a little awkward in many cases.

	Again I agree. The functions docs are insufficient for most functions
I would say.
	I like the way the Oracle functions are documented, except for the
fact that they have one huge page for all functions, which is hard on
those on slow connections reading docs online. 
	They have functions in tables grouped per functionality (e.g. character
functions that returning character values, character functions returning
number values) and with each function name (which is all that is in the
table) is linked to a larger explanation of the function with the complete
syntax and examples (usually two).
	http://oradoc.photo.net/ora81/DOC/server.815/a67779/function.htm#1028572

	-Roberto	
-- 
+----| http://fslc.usu.edu USU Free Software & GNU/Linux Club|------+
  Roberto Mello - Computer Science, USU - http://www.brasileiro.net 
      http://www.sdl.usu.edu - Space Dynamics Lab, Web Developer    
If it wasn't for C, we would be using BASI, PASAL and OBOL!



view thread (14+ messages)  latest in thread

Message-ID: <20010325092310.A8329@cc.usu.edu>
Permalink:  ../20010325092310.A8329@cc.usu.edu/
Also on:    postgresql.org/message-id/20010325092310.A8329@cc.usu.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: rmello@cc.usu.edu, tgl@sss.pgh.pa.us, peter_e@gmx.net, t-ishii@sra.co.jp, pgsql-hackers@postgresql.org
  Subject: Re: Re: [HACKERS] Re: 7.1 docs
  In-Reply-To: <20010325092310.A8329@cc.usu.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox