pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedListing SQL books in the documentation
4+ messages / 4 participants
[nested] [flat]
* Listing SQL books in the documentation
@ 2001-09-02 17:02 Peter Eisentraut <peter_e@gmx.net>
0 siblings, 3 replies; 4+ messages in thread
From: Peter Eisentraut @ 2001-09-02 17:02 UTC (permalink / raw)
To: pgsql-docs
The documentation set contains several references to commercial books
about databases and/or SQL for "more information". Most of these are
rather old by today's standards (93-97), so I think we should do something
about that. Possibilities:
a) Update the list with our favourites of the day
b) Sell advertisement spots for the documentation ;-)
c) Not list any commerical books in the documentation at all
Personally, I'm leaning towards (c) because I feel the documentation
should not be biased in that way, and it makes it look less like "we're
too lazy to document this, please read a book".
Untouched by any of this would of course be references to relevant
academic works and specific references to any kind of text to support
implementation choices, etc.
Comments?
--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Listing SQL books in the documentation
@ 2001-09-03 21:20 Tom Lane <tgl@sss.pgh.pa.us>
parent: Peter Eisentraut <peter_e@gmx.net>
2 siblings, 0 replies; 4+ messages in thread
From: Tom Lane @ 2001-09-03 21:20 UTC (permalink / raw)
To: Peter Eisentraut <peter_e@gmx.net>; +Cc: pgsql-docs
Peter Eisentraut <peter_e@gmx.net> writes:
> The documentation set contains several references to commercial books
> about databases and/or SQL for "more information". Most of these are
> rather old by today's standards (93-97), so I think we should do something
> about that. Possibilities:
> a) Update the list with our favourites of the day
> b) Sell advertisement spots for the documentation ;-)
> c) Not list any commerical books in the documentation at all
> Personally, I'm leaning towards (c) because I feel the documentation
> should not be biased in that way, and it makes it look less like "we're
> too lazy to document this, please read a book".
I agree with (c) as far as the "official" (SGML) documentation goes.
I do think we should have a page on the website mentioning good books,
but let's keep it separate from the documentation proper.
> Untouched by any of this would of course be references to relevant
> academic works and specific references to any kind of text to support
> implementation choices, etc.
Check.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Listing SQL books in the documentation
@ 2001-09-04 04:58 Thomas Lockhart <lockhart@fourpalms.org>
parent: Peter Eisentraut <peter_e@gmx.net>
2 siblings, 0 replies; 4+ messages in thread
From: Thomas Lockhart @ 2001-09-04 04:58 UTC (permalink / raw)
To: Peter Eisentraut <peter_e@gmx.net>; +Cc: pgsql-docs
> Comments?
One reason, perhaps the most important, we mentioned books at all was to
get a common set of reference material for the developers. Also, I've
found some books to be better "references" than others, though this
doesn't necessarily argue for their inclusion in a "suggested list" in
the main docs.
As Mr. Lane points out, we should have the info somewhere. OK with me if
we want to move it to the web site...
btw, the references are old, but has anyone run across a *good* new book
covering SQL99 explicitly? It may be that a 5 year accumulation of books
after SQL92 was published is sufficient to do the topic justice, and
newer books covering the same standard do not cover any new ground.
- Thomas
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Listing SQL books in the documentation
@ 2001-09-04 16:17 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Peter Eisentraut <peter_e@gmx.net>
2 siblings, 0 replies; 4+ messages in thread
From: Bruce Momjian @ 2001-09-04 16:17 UTC (permalink / raw)
To: Peter Eisentraut <peter_e@gmx.net>; +Cc: pgsql-docs
> The documentation set contains several references to commercial books
> about databases and/or SQL for "more information". Most of these are
> rather old by today's standards (93-97), so I think we should do something
> about that. Possibilities:
>
> a) Update the list with our favourites of the day
>
> b) Sell advertisement spots for the documentation ;-)
>
> c) Not list any commerical books in the documentation at all
>
> Personally, I'm leaning towards (c) because I feel the documentation
> should not be biased in that way, and it makes it look less like "we're
> too lazy to document this, please read a book".
>
> Untouched by any of this would of course be references to relevant
> academic works and specific references to any kind of text to support
> implementation choices, etc.
FYI, the FAQ mentions books too.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2001-09-04 16:17 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-09-02 17:02 Listing SQL books in the documentation Peter Eisentraut <peter_e@gmx.net>
2001-09-03 21:20 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-09-04 04:58 ` Thomas Lockhart <lockhart@fourpalms.org>
2001-09-04 16:17 ` Bruce Momjian <pgman@candle.pha.pa.us>
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