Guadron said
I think this is one of the best buys you can do, the book is clear, useful and with a just price, 100% recommendable.
D. Fish said
New to PHP and haven't touched SQL in quite a few years. I was looking for a good beginning PHP book, not overly simplified as I have some programming experience. I needed to see how PHP and MySQL were to interact and how to set up everything on my machine (Mac). I've used MANY O'Reilly books and they're always topnotch, but this one is so disappointing to me as I find it is riddled with errors and typos. It is one thing to see typos in text and another thing altogether to have to figure out what a mistake in a code example is supposed to say. I expected more, especially since it's a 2nd edition. If it wasn't for all the forums on the web, I never even would have gotten Apache/PHP/MySQL up and running. This book isn't useless. Just not good.
Gregory Houtz said
This is a good book with a nice overview of the stated subjects.
However, I cannot evaluate the application presented because the appendix on installing Easy PHP on Microsoft Windows has SO MANY ERRORS that I simply cannot get this software running. In particular the PEAR installation instructions are just completely wrong.
I will try a Linux environment next, since I can debug better in that environment.
James E. Verry said
As usual in text books, there is a lot of useless information that is not necessary, but since writers are paid by the word, this is to be expected.
I wish there was a section on MySQL commands.
Dr. Robotnik said
I really like this book--direct, no-nonsense, and intelligently written with a minimum of jokes.
One thing that seems strange, that I'm hoping someone can clarify:
In the section of chapter 8 dealing with transactions and concurrency, there is no mention of setting transaction isolation levels (SET TRANSACTION ISOLATION LEVEL command in MySQL). Instead, concurrency is achieved solely by setting table locks.
I can sort of understand this in that the authors are using MyISAM tables. But why no mention of transaction isolation levels using INNODB tables, given that this is the more standard way of dealing with concurrency issues?
Comments