Slashdot Mirror

← Back to Stories (view on slashdot.org)

MySQL 5.0 Now Available for Production Use

Posted by Hemos on from the moving-into-the-big-time dept.

chicagoan writes "MySQL AB today announced the general availability of MySQL 5.0, the most significant product upgrade in the company's ten-year history. The major new version delivers advanced SQL standard-compliant features such as stored procedures, triggers, views & new pluggable storage engines. Over 30 enterprise platform and tool vendors have also expressed enthusiastic support for the new release of the world's most popular open source database."

6 of 359 comments (clear)

  1. Re:stored procs and triggers, finally by matth · · Score: 0, Flamebait

    Stored Procs are pain my the butt. It's so much easier to just code the SQL statement into your code. If it's in a stored proc who can change it? Any one of the programmers or database administrators. If it's in MY code who can change it? ME! Yup.

  2. Re:stored procs and triggers, finally by CastrTroy · · Score: 1, Flamebait

    You know, you bring up a good point. There's going to be a lot of people who disagree with you, but I think that what you say has a lot of fact. What they really need, is a way to include stored procedures in your code, so that queries can be run with the speed of a stored procedure, but still keeping the code for the stored procedure with the rest of your code. There's no reason why you couldn't have a language construct that says, i'm starting a stored procedure here, and then process that part to create a stored procedure.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  3. Re:stored procs and triggers, finally by yamla · · Score: 0, Flamebait

    Did you not bother to read the announcement? MySQL has stored procedures. It also has views, triggers, and many more features added in MySQL 5.0.

    --

    Oceania has always been at war with Eastasia.
  4. Re:Speed and simplicity. by commanderfoxtrot · · Score: 1, Flamebait

    Got to agree with you- VIEWS and triggers are great, but stored procedures are a real pain. However, they make triggers SO powerful (check out this blog entry on synchronising Apache passwords by one of the PostgreSQL developers).

    I'd really like to know how you are supposed to edit stored procedures without programs like phppgadmin.

    --
    http://blog.grcm.net/
  5. Re:stored procs and triggers, finally by Hognoxious · · Score: 0, Flamebait
    And if the schema has to change, we have to hunt down your code and make changes there.
    Most likely you'd have to anyway.

    The best way to manage a database is to only allow applications to modify the database via stored procedures.

    SAP doesn't use stored procedures; it's all in the application - albeit a standardised part of it, provided by SAP, that you're not supposed to bypass or frig about with. That's partly historical (databases were very primitive way back when) and partly to avoid being tied to one specific database.
    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  6. Re:Big Concerns with MySQL by mattyrobinson69 · · Score: 0, Flamebait

    hmm, mysql sold a non-gpl licensed copy of mysql to sco, nothing more. somebody mod parent down.