Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • by Ovid (2709) on 2007.03.09 7:42 (#53615) Homepage Journal

    Why, why, why do people insist upon using this piece of crap database? The arguments I get into typically go like this:

    Them: "But MySQL is faster."
    Ovid: "Do you have benchmarks?"
    Them: "No, but MySQL is still faster than other databases."
    Ovid: "Have you benchmarked your app with other databases?"
    Them: "No, but others swear up and down that it's faster."
    Ovid: "So you feel that fast is more important that correct answers?"
    Them: "But I already know MySQL."
    Ovid: "That's a fair point. The Postgres client only speaks Klingon."

    Nobody seems to get that final joke. If you know MySQL, the switch to Postgres for general use takes about, oh, 30 seconds. If you know the "advanced" features of MySQL, you probably don't need much persuading to abandon it :)

    • I like the elephant moniker more than the dolphin one. Does that count?
    • /me quotes the old Quiznos commercials

      "I fear change. I shall keep my bushes."
    • I blame phpMyAdmin for the insidious spread of this crappy database.

      I chose PostgreSQL for my own project, and I haven't regretted it one bit. Plus, you can claim it's "enterprise software" to keep the PHB's happy now that it ships with Solaris 10 by default. I think you can even get a service contract with Sun for it if you want (but I'd have to double check).

      • I blame:

        1. PHP

        2. Having a company pushing it

        3. A few years there where Pg wasn't moving much

        4. Much easier to manage accounts, just connect remotely as root and start creating accounts.
    • I don't know Postgres at all, but I can imagine it's not just db "features" and semantics that differ and need to be accounted for, but also the rest of the tool chain, e.g. clients, data loaders, backup procedures, etc. that you need to re-learn.

      All databases suck, but in different ways. MySQL, however, seems special.
    • Once, I switched an entire 28-node MySQL cluster to a single PostgreSQL instance by making clever use of table inheritance and a one-liner PL/Pgsql script written in Python 3000! PG RULEZ!!