Quoting Rory Campbell-Lange <rory@campbell-lange.net>:
> Well, another approach is to provide a set of 'real-life' mini project
> examples to show the PG way of doing things, and link items in the code
> to pages in the documentation.
I totally agree. I've mentioned that before as well- I call them tech notes.
Either way, I personally think they should be on the tech docs site with the
content merged into the search engines. Linking in the docs is bad idea.
Things change over time and the docs should not need to be updated with
information that is not the actually part of the documentation.
> An example mini project would be to show PHP users a way of updating
> multiple tables from a single function call (pl/pgsql) or how to return
> page 2 of a total of 8 pages the PG way (set returning functions), or
> how to show the number of contributions each author in a list has made
> (left outer joins...).
>
> Rory
>
> On 29/12/03, Ericson Smith (eric@did-it.com) wrote:
> > What's next? Do we keep arguing about how it meets our needs now, or
> > look at moving forward to meet the needs of the next crop of new users
> > who think MySQL sucks, but need better documentation?
>
> --
> Rory Campbell-Lange
> <rory@campbell-lange.net>
> <www.campbell-lange.net>
>
--
Keith C. Perry, MS E.E.
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com
____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com