Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

No triggers, no stored procedures - no love 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • PostgreSQL is a "real" database... a valid open-source replacement for most of Oracle, while MySQL is merely a step up from using BerkeleyDB for structured storage.

    I can't recommend MySQL for any new installations any more.

    --
    • Randal L. Schwartz
    • Stonehenge
    • ..you don't always need the 'power' of databases like Postgres and Oracle.

      I still use mysql for a lot of reasons

      • Its very easy to manage, install and administer
      • Easy to secure
      • Some of the best full text searching available - far better than any of SQL Server, Oracle or Postgres.
      • Provides the features and SQL that I need for most web development tasks.
      • Very very good documentation and support.

      Don't go writing off mysql because it doesn't provide triggers or stored procedures - these are hardly requirem

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • Oh, I'm not writing off MySQL as a "real" RDBMS. I certainly didn't mean to imply that I thought MySQL sucked or anything because it lacked these features (and I'm aware they're being added in 5.x).

        The problem is that there are certain business rules we simply can't (or shouldn't) get around without triggers and so MySQL is simply out of the question. Now, if MySQL adds these features (and they get good reviews) by the time we *do* switch, I'll be happy to look again. :)

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.