Comments: Make your book upgradeable? e.g. have a release that can be optionally ring bound. Then you can insert updates downloaded and printed from the web (updates maybe available only to registered users ;) ). [1] If it's upgradeable, then release sensitive material like field,query,row,etc limits/limitations could be included. I believe info like this would go a long way towards problem+pain avoidance. Cheerio! Link. [1] If I were in the map/atlas book business this is what I'll do. Plus there'll be transparency stuff, so that I can overlay maps on maps- either corrections or political/misc info :). At 10:26 PM 12-05-2000 -0400, Bruce Momjian wrote: >I have completed the first draft of my book except chapters 18 and 20, >appendices, and index. > >New chapters include: > > Chapter 15, Importing/Exporting Data: COPY > > Chapter 16, Database Query Tools: psql, pgaccess > > Chapter 17, Programming Interfaces: libpq, ecpg, libpq++, perl, etc. > > Chapter 19, Extending PostgreSQL: New types, functions, operators > >The books is accessible at: > > http://www.postgresql.org/docs/awbook.html > >Comments welcomed. > >-- > Bruce Momjian | http://www.op.net/~candle > [EMAIL PROTECTED] | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 > >
