You said:-
>As someone aptly pointed out about seven PHP/MySQL
>book reviews ago: There are three things the world
>doesn't need more of - cars, people and "Developing
>webapps with PHP and MySQL" books.
Well, as the author of the review I thought you might like to contemplate a few points:-
1/ PHP & MySQL books sell extremely well. People want them. Therefore I can only assume they want to know which ones are worth their hard earned money.
2/ The first edition of this book was extremely well received, sold well and has a complimentary review here on Slashdot.
3/ I wrote a deliberately short review for the second edition to inform Slashdot readers as to the differences between the editions and the continuing drawbacks (though minor).
I'm sorry if you don't want more books on PHP & MySQL or more review of those books. I only write reviews for books that are published and I feel worth a look for some reason. I guess if my Amazon reviews stop getting votes and my reviews here stop creating a surge in visitors to my website and stop gaining a positive comment or two I might rethink my choice of volumes to review.
If you'd like different books reviewed then perhaps you should write a few. It seems that timothy is always looking for reviews, out of the five or six I have written so far he has only knocked back one.
Tony
Not wishing to flame but I thought I might give a little more information on this subject.
I was objecting to such things as putting all the database information into the book in more than one way and then providing all the SQL code to create the tables and indices.
This is a book on PHP not SQL. They could have indeed used the space to explain more about PHP, if required. It would have been far more useful if they had spent that space explaining some of the design decisions.
While I agree that the publishers are damned if they do and damned if they don't I believe that a book about PHP for professionals can safely leave out SQL table creation code.
Slashdot Mirror
You said :-
>As someone aptly pointed out about seven PHP/MySQL
>book reviews ago: There are three things the world
>doesn't need more of - cars, people and "Developing
>webapps with PHP and MySQL" books.
Well, as the author of the review I thought you might like to contemplate a few points :-
1/ PHP & MySQL books sell extremely well. People want them. Therefore I can only assume they want to know which ones are worth their hard earned money.
2/ The first edition of this book was extremely well received, sold well and has a complimentary review here on Slashdot.
3/ I wrote a deliberately short review for the second edition to inform Slashdot readers as to the differences between the editions and the continuing drawbacks (though minor).
I'm sorry if you don't want more books on PHP & MySQL or more review of those books. I only write reviews for books that are published and I feel worth a look for some reason. I guess if my Amazon reviews stop getting votes and my reviews here stop creating a surge in visitors to my website and stop gaining a positive comment or two I might rethink my choice of volumes to review.
If you'd like different books reviewed then perhaps you should write a few. It seems that timothy is always looking for reviews, out of the five or six I have written so far he has only knocked back one.
Tony
I was objecting to such things as putting all the database information into the book in more than one way and then providing all the SQL code to create the tables and indices.
This is a book on PHP not SQL. They could have indeed used the space to explain more about PHP, if required. It would have been far more useful if they had spent that space explaining some of the design decisions.
While I agree that the publishers are damned if they do and damned if they don't I believe that a book about PHP for professionals can safely leave out SQL table creation code.
Tony Williams