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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Answering the question (Score:1)
Re: (Score:2)
Re: (Score:1)
I would have to agree here. MySQL has warts? Really? Sure it does. That doesn't mean it isn't useful in certain situations. MySQL would not have become as popular as it is if it was crappy and didn't perform well in the area it was designed to run.
Re: (Score:1)
MySQL succeeded because historically it was easier to install and faster than any libre RDBMS, not because it wasnߣt crappy.
Re: (Score:1)
Re:Answering the question (Score:2)
Sure, for small apps, lack of replication is usually ok and a single DB server works just fine. When you're working on something a little bigger and you find yourself with 30+ DB hosts sitting behind a load balancer, you will be extremely happy with the replication options available to you in MySQL.
Again, I haven't really kept up with the advances other open source RDBMS have made in the replication arena so perhaps MySQL is not the only game in town nowadays.
Reply to This
Parent
Re: (Score:2)
Postgres replication is still a 3rd party add on, and it doesn't come with commercial support either, oh and it can be backwards incompatible in undocumented ways between releases.
Also it corrupts itself unless you vacuum the databases and is a resource hog.
Despite all that it is still the right choice for some projects, just as mysql is for others.
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;