Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • As far as I can see, you misunderstood. The article says the number of developers that they asked, that say they use MySQL, has risen to 40%, a increase by 25% from the figure of from 32%, 2 years before. And that's a relative figure, it doesn't take into account how many developers there were and are. So, the effective number of people using MySQL may have risen more, or on the contrary, less, than 25%.
  • 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.

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

      • 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.

        • 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.

          • 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.)

            • 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.