Build Your Own Database-Driven Website
Unlike the arbitrary structure exemplified by so many programmers' references, Build Your Own Database Driven Website using PHP & MySQL is written more like an instruction manual, with chapters arranged in the order in which you should use them.
The first chapter explains the installation of PHP and MySQL; the next two cover usage basics. In Chapter 4 you're already pulling information from your database and publishing it on the Web. Chapters 5-10 refine what you've already accomplished, and delve into advanced topics in both PHP and MySQL.
If you're familiar with Yank's original tutorial, on which he based this book, your familiarity will end with the closing pages of Chapter 10. Chapter 11 addresses the storage of binary data in MySQL, a topic that was of great interest to me personally as I'd never done it before. In keeping with the rest of the book, Chapter 11 is a step-by-step guide, and explains the storage of binary data in a practical, down-to-earth manner that inspires you to give the book's teachings a try. Already I'm searching for an excuse to build a system, just to experiment with what I've learned. Chapter 12 covers cookies and sessions in PHP. The usage of cookies and sessions is essential to any online authentication or shopping cart system, and this topic makes a great final chapter that complements the book's other lessons.
This book makes good on its promise to teach you everything you need to know to build a database driven Website, but fortunately for us the author decided to throw in a few extras -- these take the form of four reference appendices. Appendix A covers MySQL syntax, which, while covered throughout the book, is easily referenced through this well-organized appendix. Appendix B explains MySQL functions, while Appendix C covers MySQL datatypes in considerable detail, so much so that I found this information easier to use than the official MySQL online reference. Finally, Appendix D covers the PHP functions that are used with MySQL.
If you progress in your programming skills you'll eventually need to buy a complete programmer's reference for PHP, although you probably won't need to buy an SQL reference unless you start using a more robust database solution than MySQL. However, if you want to build your first database-driven website, or even if you have built one before but want a practical reference, I can't recommend this book highly enough. Build Your Own Database Driven Website Using PHP & MySQL will guide you step by step through the development process -- who could ask for more?
You can purchase Build Your Own Database-Driven Website Using PHP & MySQL, 2nd Ed from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
that once you learn the basics of PHP and MySQL all books on SQL/MySQL and PHP just don't cut it. You would probably be better off with the online documentation from the respective websites and for those really though cases a PHP/MySQL Cookbook.
My penguin ate my sig
I have a PHP book that's 567 pages long. I have two SQL books: one has 377 pages; the other has 719. Yet I consider 295-page 'Build Your Own Database Driven Website using PHP & MySQL' by Kevin Yank more valuable than any of these books.
Just because a book is long, doesn't mean it's useful.
like the great quote
The Ten Commandments contain 297 words. The Bill of Rights is stated in 463 words. The Lord's prayer has only 67. The story of creation in the Bible uses only 200 words. Lincoln's Gettysburg Address contains 271 words. On the other hand, a recent Federal directive to regulate the price of cabbage contains 26,911 words.
I personally find, the bigger the book, the more difficult it is to navigate and the less useful it really becomes. Quick, short, to the point explanations are almost always better than long details drawn out explanations that I don't have the time or the desire to read.
~ kjrose
You know, it might be useful if Slashdot book reviews were limited to books that are currently in print!
You have uncommented code with embedded HTML that is database specific. Don't get me wrong... if you have a small project that works with a quick hack, then that's ok.
With any modern PHP project, what's wrong with using templates, PEAR, and object oriented programming? Most PHP books out there tend to spin the mantra of PHP and MySQL or Postgresql without taking the time to show how to use PHP in a modern context where it deserves to be. Thus much PHP programming gets scoffed at because it tends to be unmaintainable.
I'm sorry, but at this point I'm unable to recommend almost any of the PHP books out there. They mostly encourange terrible PHP system development practices -- embedded HTML, database specific coding, non OOP development.
There are a few sites that are showing the light. phpclasses.org only has OOP based PHP programs and the tools you need to use templating, mailing, databases in a thoroughly modular manner, and dont forget the PEAR site which documents and make available the excellent PEAR classes for PHP.
A few other sites also are preparing PHP libraries and development environments that are a joy to work with.
For PHP public www information is better that 99% of the books out there, and in the case of this book... 100%
Newsfollow.com
I imagine most Slashdotted sites die from network starvation long before their machines come to a grinding halt.
Hi,
I bought this book a few months ago to learn just what the title says it teaches. Unfortunately, it had many, many typos in the code examples that resulted in me being stopped cold.
One would need to already know a lot about PHP to know what needed to be fixed. Sadly, there was no online "errata" for the errors that stopped me cold. I think there was an online errata, but it didn't list many of the errors that stopped me cold.
It was only due to my posting the non working code online and getting strangers who already knew PHP to point out what was wrong that I was able to proceed -- at least until the next non corrected error that stopped me cold again.
Finally, In disgust, I gave up and bought the Wrox book (by Welling?) that just came out with a second edition.
What's sad is there is no excuse for the lack of an online errata for the errors that stopped me codl time and time again. I had the latest edition of the book.
IMO, save your money and time -- buy the Wrox book instead and make PROGRESS learning PHP and MySQL.