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.
  • If the answer to the question is "MySQL" you are not asking the right question. : )
    • If the answer to the question is "MySQL" you are not asking the right question. : )
      I see the smiley face, but MySQL has served Slashdot extremely well over the years. The proof is in the pudding, no?
      • Thank you for noticing the smiley face.

        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.
        • MySQL succeeded because historically it was easier to install and faster than any libre RDBMS, not because it wasnߣt crappy.

          • I am not arguing that...but I think you will actually find people who actually like and prefer MySQL. Such is the way of things.
            • The fundamental reason we chose MySQL was out of the box replication. Now, this was a couple of years ago so other open source RDBMS might have caught up by now but lack of replication did prove to be a major showstopper.

              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 yo
              • I don't think any of the other major libre RDBMS come with decent and/or out of the box replication.

                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;
    • Or rather, chances are you're not asking the question you think you are.

      For certain problems it's obviously a good choise (in my experience it seems those problems are pretty rare though).
    • Right because :
      What libre RDBMS has Commerical Support, proven and reliable replication and backup and a decent GUI?
      is obviously such a wrong question.

      I work with MySQL and Postgres almost exclusively and have to say that 9/10 times I would choose the former over the latter - especially if I'm clustering.

      For all the talk about MySQL corrupting data it remains anecdotal and hasn't really been seen in production, fail to vacuum your postgres however and that's your data corrupted or lost.

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • That fits my experience as well. (Also, as a matter of personal preference, I don't care for the PostgreSQL CLI.)

      • For all the talk about MySQL corrupting data it remains anecdotal and hasn't really been seen in production...

        Did you mean that you haven't seen it in your production environment? I get hit with this all the time and it's terribly frustrating to get pulled away from real work only to find yet another bit of code I have to patch because the MySQL developers didn't think data integrity was important. I know I'm not the only person with this problem.