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

use Perl Log In

Log In

[ Create a new account ]

djberg96 (2603)

  (email not shown publicly)

Journal of djberg96 (2603)

Monday March 24, 2003
01:16 AM

No triggers, no stored procedures - no love

[ #11193 ]
For some reason I thought MySQL added stored procedures and triggers in 4.x. Apparently, I was mistaken. I'm glad I found out, though. One of my colleagues was thinking of switching our database to MySQL if company negotiations with Oracle broke down. Without stored procedures or (especially) triggers, I'd say there's no chance of that now.

Where does that leave us if Oracle goes bye-bye? Hmm...PostgreSQL has both. :)

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.
  • PostgreSQL is a "real" database... a valid open-source replacement for most of Oracle, while MySQL is merely a step up from using BerkeleyDB for structured storage.

    I can't recommend MySQL for any new installations any more.

    • Randal L. Schwartz
    • Stonehenge
    • don't always need the 'power' of databases like Postgres and Oracle.

      I still use mysql for a lot of reasons

      • Its very easy to manage, install and administer
      • Easy to secure
      • Some of the best full text searching available - far better than any of SQL Server, Oracle or Postgres.
      • Provides the features and SQL that I need for most web development tasks.
      • Very very good documentation and support.

      Don't go writing off mysql because it doesn't provide triggers or stored procedures - these are hardly requirem


      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • Oh, I'm not writing off MySQL as a "real" RDBMS. I certainly didn't mean to imply that I thought MySQL sucked or anything because it lacked these features (and I'm aware they're being added in 5.x).

        The problem is that there are certain business rules we simply can't (or shouldn't) get around without triggers and so MySQL is simply out of the question. Now, if MySQL adds these features (and they get good reviews) by the time we *do* switch, I'll be happy to look again. :)

    • PostgreSQL is a "real" database... a valid open-source replacement for most of Oracle, ...

      For the task of migrating an existing commercial RDBMS to an open source one, PostgreSQL is certainly the best choice today. Open Source software is nothing if not dynamic. Most people who write off MySQL do it with old information. MySQL has supported ACID transactions for a while now, and stored procs are being demonstrated live next month at the MySQL User Conference; expect stable, production-grade stored

  • No, seriously (Score:3, Informative)

    by gnat (29) on 2003.03.24 5:56 (#18240) Journal
    I hear good things about Microsoft's SQL Server. No, really. And it's a small fraction of the price of Oracle.


    • I'm not sure if I should mod this as "Funny" or "Troll" - perhaps "Funny Troll". :-P

      I have this nagging suspicion that MS SQL Server will become the replacement if Oracle goes away. SQL Server has some serious issues. First, it doesn't run on Solaris (does it?), which would mean the company would probably have to buy new hardware. Second, anyone remember Code Red?

      I can't speak for other groups in the company but I can tell you that *our group* won't be using it.

      • SQL Server has plenty of nasty dis-advantages.

        Its JDBC and ODBC drivers are second-rate.
        Its full text searching is frankly rubbish.
        Its error messages are frequently unhelpful.
        It requires a lot of hardware and nursing and coaxing into working.
        Its clustering, backup and synchronisation leave a lot to be desired as well.


        @JAPH = qw(Hacker Perl Another Just);
        print reverse @JAPH;
        • How odd. My uncle has been running it in hundreds of customer sites, managing inventory and sales for clothing retailers, and he has nothing but praise for it. As always, I guess, YMMV.


          • Indeed Mileage will vary, just more with some databases than others.

            Bear in mind also - where I worked previously was an MS shop, they had a huge number of problems with SQL Server, but the boss loved its GUI and thought microsoft could do no wrong.

            I would never reccomend SQL Server for ecommerce for the simple reason that it has severe data corruption, security and searching issues and these are critical for ecommerce.


            @JAPH = qw(Hacker Perl Another Just);
            print reverse @JAPH;
  • Stored procedures are being written into v5 of mysql.
    Were that I say, pancakes?