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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I really enjoy using SQLite, especially since all it takes from Perl is install DBD::SQLite, and the whole database gets embedded inside the DBD handler!

    Between SQLite for the low end, and PostgreSQL for the high-end, there's really no need to use the crippled MySQL for any new installations. Joy.

    --
    • Randal L. Schwartz
    • Stonehenge
    • Without getting all long and drawn out here, do you have some previous postings to point to so I can understand what leads you to state that MySQL is bad and PostgreSQL is good?

      I've skimmed over both of them slightly, and have no real opinions either way, but I don't feel like heading down the wrong track and having to back up and start over.
      • This might be slightly dated, but check out MySQL Gotchas. I consider the lack of reporting that data is too large for the storage to be showstopping, personally, even if the rest of it weren't true.

        Another showstopper is the licensing. Even the MySQL website advocates a commercial license if you're doing any sort of money making with MySQL. On the other hand, PostgreSQL is completely free, being under the free'er-than-GPL BSD license. Since I work mainly with commercial clients, this can make a diffe

        --
        • Randal L. Schwartz
        • Stonehenge
        • But no support for Windows. That is a showstopper for PostgreSQL. It is "coming" I know. I think FirebirdSQL is really good for high end stuff *and* it is cross-platform.

          I really like SQLite, as you can do some quick and dirty stuff with it.