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
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Aargh! (Score:2)
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 :)
Reply to This
Re: (Score:1)
Re: (Score:1)
"I fear change. I shall keep my bushes."
Re: (Score:2)
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).
Re: (Score:1)
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.
Re: (Score:1)
All databases suck, but in different ways. MySQL, however, seems special.
Re: (Score:1)
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!!