On 2/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"P Kishor" <[EMAIL PROTECTED]> wrote:
>
> is it possible to add usage such as the above, and many, many
> wonderful SQL suggestions routinely provided by Igor Tandetnik (thanks
> Igor!) to the syntax docs in the form of user-submitted comments?
>

I was trying to move all of the documentation into wiki for
exactly this reason.  But then people said they didn't like
that and wanted all the documentation in the source tree.
Guess you can't please everybody :-)  Right now we have some
documentation in the source tree and some on the wiki, which
I suppose is guaranteed to please nobody.....


in that case, do what _you_ want and everyone will follow -- they may
not like it, but won't be worse off for the wear. After all, you are
the creator of the software so the de facto el jefe. ;-)

I was thinking more in terms of PHP/MySQL and the new CPAN docs. There
is "official" documentation, to which users can add comments. In these
comments one finds syntax-specific gotchas, workarounds, examples,
etc. Of course, this would mean that each command gets its own page so
comments are manageable. Think of it as community annotation of the
official docs. As is, the docs are very sparse, with very few usage
examples, particularly when it comes to the use of various
expressions, and the DEFAULT syntax variation that you mentioned.

The mailing list archive has wonderfully helpful nuggets buried in it,
many of which could find permanent life on the official docs pages.

--
Puneet Kishor http://punkish.eidesis.org/
Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
Open Source Geospatial Foundation http://www.osgeo.org/education/
---------------------------------------------------------------------
collaborate, communicate, compete
=====================================================================

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to