use Perl

• Squelching shortcomings (Score:1)

  by Aristotle (5147)

  Well, each version of MySQL does squelch some of the shortcomings. The problem is how many of them there are – squelching them one by one ain’t gonna make MySQL into a solid product for another decade or two.
  • Re:Squelching shortcomings (Score:1)

    by chromatic (983) on 2007.03.25 22:19 (#53977) Homepage Journal

    I couldn't imagine doing data warehousing without a fully ACID-compliant, multi-mastered, concurrent, high-available clustering, column-locked database.

    Reply to This

    Parent

    • Re: (Score:1)

      by Aristotle (5147)

      Yeah, you’re right, sorry. Things like values being simultaneously NULL and NOT NULL or surrounding spaces implicitly getting trimmed on textual comparisons are essential to effective handling of large amounts of data. And of course everyone needs to scale like eBay before their business leaves their living room.
      • Re: (Score:1)

        by chromatic (983)

        I can write explicitly-typed Haskell code that can compile down to very fast C code while still being exceptionally safe, but sometimes I write shell scripts.

        I could definitely have used writable views in MySQL as far back as 1999, but even after making the tradeoff to do without them, MySQL was still the best choice for that application.
        • Re: (Score:1)

          by Aristotle (5147)

          When I need the equivalent of shell scripts in SQL-land, I use SQLite.

          (Doesn’t even do types, while we’re on that topic. Funny though, its coercion story is sane anyway – whereas MySQL’s, despite the presence of types, ain’t.)
          • Re: (Score:1)

            by chromatic (983)

            SQLite wasn't an option for that project (and I use it gladly for single-user projects, but not for multi-user projects).

            Oddly, MySQL's conversion rules have never ever caused errors in my projects--and I continually have to look up the SQLite syntax for using types.