Let me interject as a user:
At least document something about some of the major modules, like say:
Some moduless exist to interface to other languages like DBD::Pg
This way I as a user at least have a "shot in the dark" of knowing what to
look for on the search engines. And you won't have to maintain anything
like URL's etc for the ever changing language interfaces.
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
> -----Original Message-----
> From: pgsql-docs-owner@postgresql.org
> [mailto:pgsql-docs-owner@postgresql.org]On Behalf Of Peter Eisentraut
> Sent: Tuesday, November 27, 2001 9:37 AM
> To: Thomas Lockhart
> Cc: Tom Lane; pgsql-docs@postgresql.org
> Subject: Re: [DOCS] Documentation gap: Perl interfaces
>
>
> Thomas Lockhart writes:
>
> > ...
> > > It's not our job to tell people what the wide world of database
> > > programming has to offer. We control neither Perl nor
> the DBD:Pg driver,
> > > so if we start bothering with that then there is no
> theoretical boundary
> > > -- what about all the other Python, Scheme, Emacs Lisp, Ruby, or
> > > language-of-the-day interfaces?
> >
> > We should mention that they exist, and give pointers on
> where to find
> > them and what is involved in installing them (maybe even
> some shortcut
> > instructions).
>
> We've been there, and it all that information became outdated
> pretty soon.
> In fact we've just removed all not-included-here documentation in this
> release. There are literally thousands of packages interfacing with
> PostgreSQL, and I don't see how we're going to manage to put
> these into
> the documentation. People that are looking for software can go to
> freshmeat or the PG web site (a.k.a. elephantmeat) or other
> such places.
>
> --
> Peter Eisentraut peter_e@gmx.net
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo@postgresql.org
>