Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
PHP Books Media Programming Book Reviews IT Technology

Build Your Own Database-Driven Website 277

Chris Beasley writes "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. Why? Because, while I may find only a quarter or, at best, half of these books useful on a regular basis, all 295 pages of Yank's new release are of value to me on a daily basis."
Build Your Own Database-Driven Website Using PHP & MySQL, 2nd Ed
author Kevin Yank
pages 295
publisher SitePoint
rating 5/5
reviewer Chris Beasley
ISBN 0957921802
summary A tutorial-style book for beginning PHP/MySQL Programmers

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.

This discussion has been archived. No new comments can be posted.

Build Your Own Database-Driven Website

Comments Filter:
  • by Anonymous Coward on Thursday April 03, 2003 @10:47AM (#5652808)
    Before I read it I was successful and happy.

    Now I'm a tired bitter old man.

    Damn this book
    Damn this book to hell
  • Who wouldn't? (Score:3, Interesting)

    by eenglish_ca ( 662371 ) <eenglish@@@gmail...com> on Thursday April 03, 2003 @10:48AM (#5652821) Homepage
    Who wouldn't build their own database website. Imagine slogging through hundreds of pages of fixed html. Does anyone know of sites like these other than personal pages put up by newbies? All of my sites are at least dynamic using php.
    • Re:Who wouldn't? (Score:2, Insightful)

      by ozbon ( 99708 )
      In fairness, sometimes it depends on whether your hosting service bungs in PHP etc. free, or at extra charge. It's all part of the pros and cons when it comes to dealing with hosting services.

      Personally, I prefer the ones that do throw in mySQL/PHP/etc. in with the deal - but there's a lot out there that dont, EasySpace [easyspace.com] being one of them. Yeah, I used them for a while, but now I don't - but they still charge through the nose for mySQL and PHP stuff, as well as most other things.
    • Re:Who wouldn't? (Score:5, Informative)

      by K. ( 10774 ) on Thursday April 03, 2003 @10:53AM (#5652880) Homepage Journal
      Preprocessing pages and serving static html is one way of coping with high CPU loads incurred by having a popular dynamic site. So as in everything, the best path is the middle path. Or so my teacher Steven Seagal tells me.
    • You're probably right. Of course, it does involve learning a bit of code, and there are plenty of people who aren't comfortable with that.

      And then there are those who have small sites with only a couple of pages that don't need to change very often. Not much call for PHP on those.

    • Re:Who wouldn't? (Score:4, Insightful)

      by jest3r ( 458429 ) on Thursday April 03, 2003 @11:16AM (#5653059)
      when you actually start getting alot of traffic it is sometimes best to use static pages for as much content as possible .. of course these static pages are generated from information stored in a database ..

      opening a database connection for every visitor on every page is suicide if you only have a single server .. and your site is featured on slashdot ..
      • Re:Who wouldn't? (Score:5, Interesting)

        by rreyelts ( 470154 ) on Thursday April 03, 2003 @12:12PM (#5653507) Homepage
        opening a database connection for every visitor on every page is suicide
        Rather, just about every serious web application requires database access, and yet they don't commit suicide. It's called connection pooling, and it is a standard feature on pretty much any application server nowadays.

        I imagine most Slashdotted sites die from network starvation long before their machines come to a grinding halt.

      • Re:Who wouldn't? (Score:3, Insightful)

        by markv242 ( 622209 )
        "opening a database connection for every visitor on every page is suicide if you only have a single server .. and your site is featured on slashdot .."

        Um, no.

        Real database connection pools (say, JDBC) running through a real application server (say, Resin) instead of a compiled-into-Apache-interpreter (PHP), accessing a robust database (Oracle) can and will run at an extremely high speed even when heavily loaded via Slashdot, etc.

        All of these "create your own database-driven site!" beginner books are r

        • Of course, convincing Mom and Pop to license Oracle for their recipe website might be a little difficult....
        • The problem with this is that not many people can afford the expensive programs you mention.

          What's more, there aren't any "Build Your Own Database-Driven Website With PHP and PostgreSQL" books, so you get idiots who can't even bother to write proper HTML suddenly thinking that they can do an enterprise-level site using nothing but PHP and MySQL. MySQL is such a half-assed database that it's embarrassing, yet unless you run your own server, that's pretty much what you're limited to because that's the only D
    • Why would anyone NEED their personal site (ie, here's who I am, here are links to my friends pages, etc) to be dynamically generated? For that matter, why should a page be written to be dynamic if it only changes, say, every 6-8 months? I've seen a lot of people build their sites using php/flash/perl/java/etc when it could have been done more easily and just as effectively with plain html.

      I'll grant you, though, that for a business page, or something that updates on a daily/weekly basis, static html is p
      • Re:Who wouldn't? (Score:4, Insightful)

        by jandrese ( 485 ) <kensama@vt.edu> on Thursday April 03, 2003 @11:56AM (#5653403) Homepage Journal
        It all depends on what you're doing. Most business pages (brochurepages) are actually quite static and would not need much automation.

        On a counterpoint, some homepages have dynamic content of some sort that you just can't do with static HTML. It's all a matter of what you're doing, not who you're doing it for.

        Also, some people put up private pages as a way of teaching themselves the ins and outs of running webpages. Those pages can quickly include all sorts of bells and whisles including dynamic content, flash, etc. Additionally, those sights can look good on a Resume since it shows the person has enough interest in the technology to play with it outside of the workplace.
      • Ther eis a place for PHP when having a dynamic back end to a static or semi-static front end.

        Personally I use mod_perl to maintain a cache. The backend PHP will clear the cached pages as necessary. If an uncached page is requested mod_perl passes it on to PHP to generate it and pops a copy in the cache.

        My clients can then update their contents (job adverts) as often as they like and my site will keep the navigation menus up to date.

        I also scrape content from our partners.

        In this way I can forget about t
      • Its nice when you can give access to write some of those html files to your 'friends' without giving them FTP access to your server.

        Dynamic content with web-based multi-user editing is why I use php/sql on my somewhat smallish site.
    • Re:Who wouldn't? (Score:4, Insightful)

      by ncc74656 ( 45571 ) <scott@alfter.us> on Thursday April 03, 2003 @12:00PM (#5653431) Homepage Journal
      Who wouldn't build their own database website. Imagine slogging through hundreds of pages of fixed html. Does anyone know of sites like these other than personal pages put up by newbies? All of my sites are at least dynamic using php.

      It depends on what type of content you're putting up. I wanted consistent navigation from page to page and easier maintainability; server-parsed HTML is sufficient for that task. It also allows me to serve up either proper HTML and CSS for browsers that can handle it [mozilla.org] or broken, non-standard HTML for crappy non-standards-compliant browsers [netscape.com]. While I use MySQL for logging server activity (when I dumped access_log into the database, the database was smaller than the text file that created it), the only "content" I've ever served up from it was statistics of how many tens of thousands of times infected IIS machines had tried to pass their bugs on to my server (done with server-parsed HTML and a shell script with the query). For mostly-static content on a small to medium website, is there any reason (other than "because I can") for shoving every website into a database?

      All of my sites are at least dynamic using php.

      Such as this one [windsurf.dyns.cx], which took forever to load because the images appear to have not been optimized? Looks like invalid HTML [w3.org] with a big table in it.

      (Why do I get the sneaking suspicion I've just been trolled?)

    • Who wouldn't build their own database website. Imagine slogging through hundreds of pages of fixed html. Does anyone know of sites like these other than personal pages put up by newbies? All of my sites are at least dynamic using php.

      You make things as flexible and dynamic as possible on your (the webmaster's) end, then you process everything into static pages. This moves all of the heavy-lifting offline. This will cover most sites.
  • Chapter 16 (Score:4, Funny)

    by SpanishInquisition ( 127269 ) on Thursday April 03, 2003 @10:48AM (#5652829) Homepage Journal
    Avoiding the "Slahdot Effect"
    • by Sleepy ( 4551 )
      > Avoiding the "Slahdot Effect"

      Were you refering to the Slashdot-caused bandwidth spike?
      Or did you mean the "I can't spell" Slahdot effect?

      Sorry... it's so unclear what you meant.. :-)
  • The thruth is... (Score:5, Interesting)

    by dfiguero ( 324827 ) on Thursday April 03, 2003 @10:51AM (#5652860)
    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.

    • Re:The thruth is... (Score:5, Interesting)

      by gid ( 5195 ) on Thursday April 03, 2003 @11:43AM (#5653290) Homepage
      I've run into the same thing. In fact, I've taken it one step further, I have NEVER felt a I needed a book to teach me PHP/MySQL, both projects have fantastic online documentation. If there's something that the PHP documentation doesn't tell me, chances are the user comments do. There hasn't been one feasible thing that I haven't been able to figure out with PHP or MySQL thru the online documentation.

      The interesting thing is, I've recently have had to start learning Java / JSP / PL/SQL / Oracle. Documentation is a nightmare. There just doesn't seem to be one end all be all on stop shop for my Java documentation needs, there's about 20 relevant manuals that I need to sift through to find out one thing, and there's about 20 different ways to implement your site. Ok are we going to build our own tag libraries, conform to J2EE, use java beans, just do straight jsp, on what classes should we make and for what? What stuff should be stored in PL/SQL, etc etc etc. It's crazy.

      PHP is a dream come true, ease of use wise. It may not be the fastest thing in the world since it's just a scripting language, but there's the Zend caching engine that can help quite a bit. There's just something to be said for reading PHP code from top to bottom and know exactly what's going on. And being able to pay a cheap PHP monkey to code your site for you, instead of paying an expensive Java/Oracle programmer with 10 years experience.
      • I agree wholeheartedly. Oracle's docs suck. Their developer site sucks. ... this may not be a popular comparison, but Micrsoft's docs are way better. I can't tell you the number of sample java classes I've gotten from Oracle's site/docs which don't COMPILE due to a syntax error, let alone actually WORK.
    • I've been trying to learn PHP/MySQL for about a year now, using only online documentation. Heres the problem I have with that ...

      I am not a programmer.

      So when the documentation is telling me what something does, RARELY does it provide an example that makes sense. it's all documentation for programmers, outlining functions and classes and things I've never heard of ...

      I want to learn PHP/MySQL because I want to be able to build tools to use as a sysadmin, and for fun, but most tutorials are made for pe
  • by Anonymous Coward on Thursday April 03, 2003 @10:52AM (#5652866)
    all 295 pages of Yank's new release are of value to me on a daily basis.
    Maybe you just need a better long term memory.
  • sounds simliar (Score:3, Interesting)

    by drgroove ( 631550 ) on Thursday April 03, 2003 @10:52AM (#5652872)
    to the PHP and MySQL Web Development book by Welling & Thomson, from SAMS.

    Good to see more 'tutorial' style books coming out - its the real world examples that springboard a beginner's skill level w/ a new language.

    I'd much prefer to see this type of tutorial book in the hands of a n00b than a straight-lexicon or syntax book w/o examples of actual apps you can build. Sounds like a good one, based on the review.
  • leave it to open source (mySQL) to remove the bloat.....

    xao
  • Sounds good... (Score:4, Insightful)

    by Randolpho ( 628485 ) on Thursday April 03, 2003 @10:59AM (#5652929) Homepage Journal
    ... but aren't there already a bunch of books that do this? I mean, wouldn't a more useful book be one about *designing* a database driven site? Stuff like content management, implementing full text search, session tracking, user logins, site organization and navigation, that sorta thing?

    I mean, do we really need *another* book that tells you how to program in PHP and how to use MySQL?

    Anyway, from the review, I suppose this would be a good replacement for those books. I just think what we need is something more.
    • Re:Sounds good... (Score:3, Insightful)

      by drgroove ( 631550 )
      ... but aren't there already a bunch of books that do this?

      Yes, but having a choice of books is helpful to beginners; especially considering that not every author's writing style or code examples work for every budding developer out there. Choice is good. There is still plenty of room for the improvements you sighted, tho, but I don't think that lack of coverage on those concepts in this particular book denigrates its quality or usefulness.
    • it would be nicer if people would spend a day of there life to look at postgresql... now I was one of the MySQL fanatics that hated pg.. how foolish I was.. trust me, all this hype over MySQL is totaly unjustified, postgresql is a far far better rdbms. Dont believe me? take a day to look up its features, you wont regret it.
      • one feature of MySQL is that it "runs" on Win32 platform a little easier than pgsql, but i totally agree with the need for people to consider postgresql. with the use of adodb for php (database abstraction layer), use of pgsql is much easier.
        • win32? pdp11? unix? linux? doesn't matter -- firebird [ibphoenix.com] does it all. postgresql and firebird are quite similar, feature-wise, but their histories are quite different. check it out! (and yes, firebird/interbase -are- supported by php.) i just don't get the obsession with mysql, as if it were the -only- usable open-source database out there. btw, i might love postgres more if it didn't take more work to install than firebird. i mean ... firebird just -goes-. and that's on linux (production machine) or windows (
    • Disclaimer: I don't write php for a living, but I do write C/Perl.

      People need a book that lets them understand what the hell is going on when they re-use someone else's code. Everything I've ever done for myself or others in php has basically been code-reuse. Download the phpnuke or postnuke scripts, configure it then edit the ones to fit some dynamic modules that you need specific on your site. I have never ran into anyone that has ever written a php/mySQL application from scratch, and why would you when
  • Affiliate link? (Score:2, Insightful)

    by Anonymous Coward
    Putting an affiliate link makes the review so much more credible.
  • All 295? (Score:3, Insightful)

    by ejaytee ( 186527 ) on Thursday April 03, 2003 @11:02AM (#5652949)

    All 295 pages, every day? Wow... the only way this would be true for me is if I forgot how to count all the way up to 295 and had to make use of the page numbering.

    Seriously, will somebody reset the hyperbole detector? Mine keeps going off.

  • by MarvinMouse ( 323641 ) on Thursday April 03, 2003 @11:03AM (#5652964) Homepage Journal
    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.
    • Philip and Alex [greenspun.com] covers the same topic (building a website with a database backend). It has a large number of pages which are not at all useful because they are colour photographs of Alex or of various parts of North America. And others are random sidetracks or rants against the stupidity of web designers or 'junkware'. But they are not wasted pages because they are entertaining to read or look at.

      To avoid are books with a large number of pages which are neither useful nor entertaining - like most of the
    • I personally find, the bigger the book, the more difficult it is to navigate and the less useful it really becomes.

      mega biblion, mega kakon - Kallimakhos, one of the librarians of the Library of Alexandria. The Greek is easy enough you can probably figure out what it means on your own without knowing Greek; kakos means "bad."

  • save your money (Score:3, Informative)

    by larry bagina ( 561269 ) on Thursday April 03, 2003 @11:03AM (#5652965) Journal
    I looked through this book at barnes & noble a couple weeks ago. I'd recommend skipping it, although it may be useful for some newbies.


    Basically, it's a tutorial (build a php/mysql website in 10 steps!). There are plenty of online resources (like devshed) that do tutorials like this all the time. (Note to slashdot editors: devshed spell checks submissions!). If you like to read on the john, this book might be for you. Chances are, you'd be better off to save your money for a mysql or php reference book.

  • by Anonymous Coward on Thursday April 03, 2003 @11:04AM (#5652978)
    I just looked at Barnes and Noble [bn.com] and found the book is no longer available! [barnesandnoble.com]


    You know, it might be useful if Slashdot book reviews were limited to books that are currently in print!

  • by webword ( 82711 ) on Thursday April 03, 2003 @11:04AM (#5652982) Homepage
    Forget PHP. Use Whitespace [slashdot.org]! If that is too hard, install FrontPage! The real l337 h4x0r solution.
  • by Anonymous Coward
    it's based on a very popular article series he did for sitepoint.com and other sites. I dl'd and printed out all of those articles that comprise the base of the current book and they are dog-eared and well worn. I especially like his tone througout the articles (nice sense of humor) and concise coding style well explained. I will 'browse' this book at Bordersss if they have it and if I see new stuff I will buy it.
  • "...all 295 pages of Yank's new release are of value to me on a daily basis." While regular bowel movements are to be encouraged, you'll find toilet paper to be more cost-effective.
  • by The-Perl-CD-Bookshel ( 631252 ) on Thursday April 03, 2003 @11:08AM (#5653006) Homepage Journal
    I develop 'AMP' solutions and IMHO this book, in addition to the PHP cookbook, are the best two books you can buy on the subject. You can really tackle most any problem with these two books and if you cant, there is always IRC or as a last resort the documentation :)
  • by British ( 51765 ) <british1500@gmail.com> on Thursday April 03, 2003 @11:10AM (#5653019) Homepage Journal
    It seems too many websites out there have mile-long URLs(including huge session ID strings) and other gizmos only to deliver the same static content over and over again.

    What ever happened simply to static web pages that are nice and simple, and dish out the data without all that overhead?
    • What ever happened simply to static web pages that are nice and simple, and dish out the data without all that overhead?

      Or better yet a set of simple, concise data files and a batch method for converting it to static HTML after updates for display on the web. What's this internet coming to?
      • Or better yet a set of simple, concise data files and a batch method for converting it to static HTML after updates for display on the web. What's this internet coming to?

        Actually, I started out developing my website with every single page being dynamically generated using a cgi script. I did it mostly because it was 'cool' to have a 'dynamic' website. I quickly realized that my pentium 166 mHz (which is my webserver) wasn't doing so hot serving up lots of dynamic pages. So it took a slow computer to ma

      • Or better yet a set of simple, concise data files and a batch method for converting it to static HTML after updates for display on the web.

        Sounds like you're talking about Bloxsom [raelity.org].

    • Chapter 11 is a step-by-step guide [...] searching for an excuse to build a system
    • MT [moveabletype.org] does just that and is widely used by the blogging community.

      There are many plugins [mt-plugins.org] available for it, too.

      All you need is CGI (perl) support on your server -- it doesn't require a database and the site it generates is based on static pages (partially) updated every time the admin makes a change.
    • If you've got no content, your site doesn't need to be dynamic. A static blank page will do.

      On a more serious note, it depends on what the site does. Having built a fair number of sites--both for myself and, as part of my job, for big companies--I can say there are pros and cons to driving your site from a database.

      Databases are primarily useful when you have a consistent structure to your content and you need to be able to update that content easily. When I built this site [fractalus.com] it was done from a database, bu
    • If you truly have static content, then of course you can just serve up generic pages. But I can tell you the number of Web sites that have changing content far outnumber the ones that are static (or at least they should if people would update their damn site already!).

      Even if your pages are relatively static information, if you want to change the design for 100 pages, it becomes a real pain in the ass to manually go through and change them one by one. You can use SSI for a very small percentage of cases
    • by Animats ( 122034 ) on Thursday April 03, 2003 @01:43PM (#5654360) Homepage
      There are lots of good reasons for database driven web sites:
      • Easier support for "124 people have accessed this site since January 1, 2000".
      • Three words: "customized ad content".
      • A new fortune every time!
      • "Welcome back, (Your name here)".
      • Different users, different prices.
      • Kickbacks from database sales rep.
      • Job security.
    • Apple.com's products pages are a perfect example of successful static pages, with short, rememberable URLs. Their support site dynamic, but the URLs are still short. When all you need is a simple brochure, static is often the way to go.

      Belloc
    • Well, if people weren't so damn opposed to Cookies, there wouldn't be a need for "mile-long URLs(including huge session ID strings)".
  • by teslatug ( 543527 ) on Thursday April 03, 2003 @11:10AM (#5653021)
    The book is apparently not available at BN, so I checked Amazon, and they have it [amazon.com].
  • Damn... (Score:2, Funny)

    by grub ( 11606 )

    ... I can't find the PDF on kazaa yet..
  • Third article in the last couple of weeks about yet another PHP + MySQL book. They all seem to be for the newbie's too. How about representing some other languages, other databases and some advanced techniques.

    Maybe I'm just bitter because of my extreme hatred for PHP.
  • by TheAngryMob ( 49125 ) on Thursday April 03, 2003 @11:28AM (#5653150) Homepage

    Sitepoint (the publisher) has them here [sitepoint.com]. The downside is you have to give them your email address first.

  • Is it just me, or does anyone else notice that there's a PHP/MySQL web app book review once a week. I realize that there is more than one book out there that covers this stuff, but still...

    http://slashdot.org/search.pl?query=php+mysql&op=s tories&author=&tid=&section=books&sort =1

    I'll be honest, I'm just bored of seeing reviews of yet another PHP/MySQL book every few days.

  • by esconsult1 ( 203878 ) on Thursday April 03, 2003 @12:02PM (#5653446) Homepage Journal
    One reason why PHP gets such a bad undeserved rap, is because much of the PHP code that's written out there today is a nightmare.

    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 [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 [php.net] 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%

    • OOP and server-side web site scripting is generally a bad idea. I've never seen an application in which it scales well, or is remotely possible to maintain. In fact, I was with one small company where one blowhard (much like yourself) convinced them to do the whole website with OOP. Well, the website was behind schedule and over budget enough that the company folded. So much for OOP.
      • Hmm.... I don't question your experience... but I've found that if a server app is written using classes and such it's much easier to go back and plug in a SOAP wrapper to the "business objects".

        For example, GForge [gforge.org] has a bunch of classes that we've wrapped via SOAP, so now a Java client can do something like:

        Client c = new Client("my.gforge.host", "myproject");
        client.login("tom,"fiddlesticks");
        Bug[] bugs = client.getOpenBugs();

        Fun stuff!

        Yours,

        Tom

        • Well, a wrapper around objects is one thing. Using objects can be great (I use COM objects all of the time), but using strict OOP for something as simple as, say, a web-based shopping cart is entirely too much overhead and complexity. On large volume sites, generally the extra code and the object creation/destruction is enough to drag down the performance of the whole app. OOP purists don't like it, but basic server-side scripting with includes, stored procs, and embedded HTML works very, very well.
      • And I've been in situations where someone said 'we have to use ASP/MS technologies'. Then the site got way behind schedule and yes, eventually, the company folded. So much for ASP.

        ???

        OO code can be written as poorly as procedural if people don't understand how to model the particular data in a good way *for the project*. It's just another skill. I'd take well done procedural PHP over hacked/crap OO PHP of course, but ideally, well-written OOP is both maintainable and easy to work with.
    • 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 agree 100% with this. I started with php but have moved on to mod_perl, mostly because php books encourage lazy, one shot coding. I've got hundreds of lines of code I am rewriting right now because I have to switch from MySQL to Postrges. If only I wou

    • Please don't spring new acronyms upon us without defining them. Not all of us are clued into the PHP world, and all its pet names and acronyms.
  • by Anonymous Coward on Thursday April 03, 2003 @12:14PM (#5653525)
    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.
  • Though slashdot was certain that I could:

    You can purchase Build Your Own Database-Driven Website Using PHP & MySQL, 2nd Ed from bn.com.

    Barnes and Noble assured me that, indeed:

    Not Currently Available. A new copy is not available from Barnes & Noble.com at this time. A used copy may be available from our network of book dealers.

    I cannot. There is one used copy of the book available. If they knew they had the only copy, it'd probably be on e-bay.

  • by SailFly ( 560133 ) on Thursday April 03, 2003 @12:42PM (#5653847) Homepage
    Does anyone here use Smarty? We love it, and have found it to be a wonderful template engine.
    It has a great user manual, but I would welcome a good PHP book that deals with Smarty templates.

    smarty.php.net [php.net]
  • Avoid "PHP and PostgreSQL - Advanced Web Programming" [sams.com] by Ewald Geschwinde and Hans-Jürgen Schönig [Sams 0-672-32382-6]. This book is infected with enough misprints and errors to render it unusable, but at 770+ pages, at least it's bigger'n yours. More 'spensive too. neener-neener-neener.
  • You can buy the book directly from the publisher ($34.95): http://www.sitepoint.com/books/ [sitepoint.com]

    The home page [sitepoint.com] of SitePoint has a lot of articles on planning, designing, and coding (client- and server-side) for the web.

    There's even a picture [sitepoint.com] of the pretty-boy author.
  • I cannot believe. There are tons of PHP, MySQL, and PHP+MySQL book. There tons of online discussions about that PHP and MySQL are very primitive, limited restricted and sometimes even dangerous technologies. There are very few books about PostgreSQL, Python and Zope. There tons of online discussions about that PostgreSQL, Python and Zope are superior technologies. Meanwhile new books are still published on the market, sold on book stores and reviewed on Slasdot for PHP/MySQL. Why?

    The only explanation I ca

  • by Anonymous Coward
    It seems the only jobs available in PHP and MySQL is in writing books about PHP and MySQL because there are more books than there are jobs

Talent does what it can. Genius does what it must. You do what you get paid to do.

Working...