* Say goodbye to the index subcontractor, and as an idea: Why not a mini-CD, or a downloadable file with the index? (editors: thought in that, but please, not patent it, the idea is mine :-))
As Samuel and James also feel that the index is poor, then it clearly needs some improvement. I will forward this to my editor so that they can hopefully address this not only in this book, but other books as well. I will also start looking at the index file and try to make it better myself. Perhaps I can get Apress to put the updated index online and any suggestions you or other readers have can be quickly updated. Or, barring that, if they let me, I will host the updated index myself. Perhaps I could even put the index in a SQLite database, which you can download and query. Thanks also for all the other suggestions. I am glad to know about the parts of the book you found helpful. They happen to be my favorite parts as well, and I enjoyed writing them the most. As for more code examples, I've been threatening to put more examples on my website for months now, along with other things (including coverage of new SQLite features not covered in the book such as virtual tables). But, I've been very busy with family and work. Nevertheless, I will start addressing that this weekend and try to get more helpful stuff on-line. I will get back to you about the index. I also would like to invite anyone else who has any specific things they would like to see changed in the index to tell me. Assuming I can get a revised index out electronically, I will make any such changes immediately to the file I have on-hand. -- Mike On 3/9/07, A.J.Millan <[EMAIL PROTECTED]> wrote:
>.For the record, Apress had the index generated by a third party. I've >used the index myself recently, and frankly it worked for me -- I >found what I was looking for. >The SQL and C API references to which you refer --- taken from the >on-line documentation --- start on page 365. Furthermore, the >inclusion of this material was and has been considered useful by >everyone who reviewed the book, as it serves as an authoritative and >succinct reference. Many technical books include a reference similar >to this as a convenience to the reader. >I devoted 100 pages on the subject of SQL. I tried to systematically >and progressively describe SQL so that someone completely unfamiliar >could read the chapter in order, and by the end of the chapter >understand topics such as 3NF, left outer joins, and the intricacies >of NULL. >For an average programmer who needs to use SQLite, I hope this book >can save a lot of time whether you are a unfamiliar to or experienced >with SQL or the SQLite API. I wrote this book purely because I like >SQLite, wanted to help get the word out, and someone presented me with >the opportunity to write a book. Once I decided to write it, I went to >great lengths to write a book that would be genuinely useful. Apress >has put a lot of time and effort into making this a useful book as >well. >As I said in the book, and I think on this list, I am always open to >suggestions and feedback. If you really feel the book has failed you >in some way, or missed an important topic, I would like to know about >it so I can try to make it better should it ever make it to a second >edition. While I have many other things going on in life just like >everybody else, it is important to me that the book serves its >purpose, and I am more than happy to take whatever efforts required to >do so. >-- Mike I wish remark that my message should be interpreted in its context; it is and advise to somebody for what the acquisition of the book can suppose a great economic effort. In other circumstances the advice can be different. Go ahead that, in my case, I have never acquired a book the one that cannot say that I have learned something, or that it didn't contain something valuable that had not found in any other one. I also want to pick up your's offer to add some personal suggestion in this respect (IMHO): * Eliminate the part devoted to the SQL generalities. In my opinion, the buyer of a book whose title is "The Definitive Guide to SQLite", doesn't want an introduction to the SQL; for that there already exist good manuals, even in the Web. In the best case, a chapter dedicated the SQL "peculiarities" of SQLite. * I'm not against cut and paste the SQL reference or the C-API from the on-line manual (it is really a convenience for the reader), but include an example, that can be synthetic and not commented, in each epigraph. This gives true utility. * Say goodbye to the index subcontractor, and as an idea: Why not a mini-CD, or a downloadable file with the index? (editors: thought in that, but please, not patent it, the idea is mine :-)) * More and more and more... code examples Finally, if you wants a gift for the hearing, I will tell You that indeed, I find some parts stupendous. For example, the epigraph "The thing called NULL", or the explanation of the supported data types (Storage Classes; Manifest Typing, and Type Affinity). All the chapter 5 "Design and concepts"; chapter 6, "The Core C API"; chapter 7, "Extension C API", and, of course, the chapter 9 "SQLite internals". These last chapters should be more cared and enlarged, because it is the core of the book. Greetings. A.J.Millán ZATOR Systems. P.D: excuse my English. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
