in reply to MySQL Book and PHP vs Perl

Paul DuBois's books on the subject are widely considered excellent. I've even seen them called the best entry-level technical books on any tech topic. He discusses both Perl and PHP at length.

Side stepping that. I like MySQL. I use MySQL and have for years. I would recommend if you're starting from scratch that you go with PostgreSQL instead. I would also recommend Perl over PHP but PHP is awfully convenient and well supported on budget hosts. If you just want to get going and do a little hacking: PHP. If you think you have a future in this stuff and plan to take it deeper: Perl (it's a superior jumping off place for *many* technical issues and even other languages). Also, it's easy, and natural at first, to write insecure code with databases in any language. Make sure to search for tutorials on security and SQL injection attacks.

Have fun.

Replies are listed 'Best First'.
Re^2: MySQL Book and PHP vs Perl
by bluethundr (Pilgrim) on Oct 08, 2009 at 17:57 UTC
    Well said, and thank you! Well if you wouldn't mind answering another question... what book to get started in Postgress can you recommend over the others? Also, would you care to elaborate on why PosgreSQL over MySQL? The benefits I've heard for MySQL are small, fast, easy. What are the benefits of PosgreSQL? Thanks!
[reply]

      For Postgres reading material, I'd suggest the Postgres docs themselves: They are through, and easy to find stuff in. (At least for me. I find the MySQL docs horrible.)

      Add to that some general database books if you have never worked with databases before. Sorry, I don't have any recommendations for those.

      As for benefits: It scales better to large datasets, it has a fuller selection of database features, and it operates very close to the official spec for SQL. (Where MySQL deviates fairly widely from it on occasion. Which can be nice on occasion, but it means you'd be learning bad habits in those cases.)

      If you just want to learn, and are really care about 'small, fast, easy', SQLite might also be worth a look. There isn't a smaller database out there, it's still very fast, and it's definitely the easiest to set up. But it has a very different audience. (Although it follows the SQL spec better than MySQL, and has some features MySQL is missing...)

      I've also found either of the above much easier to use and install with Perl than MySQL, but that seems to be a fairly local thing. (Although the DBD::Mysql docs have huge 'if it doesn't work' sections...)

[reply]

      :) That reminds me of the story about the drunk crawling around one night under the street lamp. Passer-by asks, "What are you doing?"

      Drunk replies, "Looking for my car keys."

      "Oh, you lost them here?"

      "No. But this is the only place with enough light to look for them."

      Based on books (and maybe even documentation) alone, MySQL could be a better choice. I don't know any Postgres books to recommend. Someone will probably come to your rescue here though. There are quite a few monks who prefer the engine. The good news is, there's not really a wrong choice. You'll find plenty o'discussions here on the topic.

[reply]

In Section Seekers of Perl Wisdom