Slashdot Mirror


MySQL's Creator On Why the Future Belongs To MariaDB

angry tapir writes "When Oracle purchased Sun, many in the open source community were bleak about the future of MySQL. According to MySQL co-creator Michael "Monty" Widenius, these fears have been proven by Oracle's attitude to MySQL and its community. In the wake of the Sun takeover, Monty forked MySQL to create MariaDB, which has picked up momentum (being included by default in Fedora, Open SUSE and, most recently, Slackware). I recently interviewed Monty about what he learned from the MySQL experience and the current state of MariaDB."

208 comments

  1. 10.0.1 Alpha by Anonymous Coward · · Score: 1

    That will show them, huh?

    1. Re:10.0.1 Alpha by wmac1 · · Score: 2, Insightful

      Why the Future Belongs To MariaDB? Because he will sell it to another company and will become rich again? That's about his future I guess.

    2. Re:10.0.1 Alpha by Anonymous Coward · · Score: 3, Informative

      Except that he can't. MariaDB is a fork of MySQL and as such Monty does not own the publishing rights in order to sell them. He could sell a "license" of MariaDB, just as he could also sell a "license" of Linux, but he can't alter the licensing of MariaDB any more than he can alter the licensing of MySQL anymore, nor can he sell those privileges to others.

    3. Re:10.0.1 Alpha by wmac1 · · Score: 1

      The least he can sell is the brand name MariaDB and the open source operation (i.e. support etc.).

  2. You gotta be kidding me. by Anonymous Coward · · Score: 0, Flamebait

    MariaDB is for lamers. Informix is where it's at.

  3. Don't forget Arch Linux by Peetke · · Score: 5, Informative

    Arch Linux also made the switch three days ago: https://www.archlinux.org/news/mariadb-replaces-mysql-in-repositories/

    1. Re:Don't forget Arch Linux by Anonymous Coward · · Score: 1

      Don't forget Poland!

    2. Re:Don't forget Arch Linux by White+Yeti · · Score: 2

      Enough of what NOT to do... Remember the Alamo! Remember Goliad!

  4. stirring the pot by Anonymous Coward · · Score: 5, Insightful

    Personally I think the future belongs to Postgres. :)

    1. Re:stirring the pot by isopropanol · · Score: 1

      Word. I prefer Postgres. But then again I have not done a comparison in a very long time. I know that MySQL (and by extension MariaDB) has been ACID compliant for several years if you pick the right backend, but does anyone know if either supports Views and stored procedures?

    2. Re:stirring the pot by dmgxmichael · · Score: 4, Informative

      Both support views and stored procedures and have since version 5.

    3. Re:stirring the pot by isopropanol · · Score: 1

      Cool, thanks. it's been a while since I did a complicated DB project; perhaps it's time to fire up a VM and try 'em out. How about triggers?

    4. Re:stirring the pot by Aaden42 · · Score: 1
    5. Re:stirring the pot by drfrog · · Score: 2

      postgresql+1
      just because something is popular doesnt make it the right choice

      AFAIK mysql/maria still relies on innodb for transactions ! plus all the myriad of mysql type mishandling of null values.
      its a horror show of popularity.

      use a proper database and stop having to work around dysfunctional programming

      --
      back in the day we didnt have no old school
    6. Re:stirring the pot by dmgxmichael · · Score: 1

      Yep, they're there - though I think they didn't show up until 5.1.

    7. Re:stirring the pot by bluefoxlucid · · Score: 2

      As a long-time MySQL fan... yes. PostgreSQL is better in basically every way.

    8. Re:stirring the pot by Dresden+Sparrow · · Score: 1

      Agreed! Less of a mess, more of a product.

    9. Re:stirring the pot by CastrTroy · · Score: 3, Informative

      Actually MariaDB and Percona both support XtraDB which is a transactional backend that's a drop in replacement for InnoDB. MariaDB also supports the new Aria storage engine which can be both transactional and non-transactional depending on your needs (determined by option in Create Table statement).

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    10. Re:stirring the pot by Anonymous Coward · · Score: 0

      InnoDB and MyISAM are the far two most popular.

      they both support views and SProcs. Neither have materialized views, though :( [not without setting your own triggers, anyways]

    11. Re:stirring the pot by wmac1 · · Score: 1

      1- Popularity among technical people "might sometimes" mean more people have found the specific product suits them.

      2- MySQL is available on almost every shared and dedicated hosting service. PostgreSQL is rarely available on shared services. I have developed a small web based ERP but I was forced to go with MySQL since most of my potential customers would want to run it on shared services.

      3- dysfunctional programming?!

    12. Re:stirring the pot by pspahn · · Score: 1

      Except when it comes to names. MySQL is clearly the better name.

      --
      Someone flopped a steamer in the gene pool.
    13. Re:stirring the pot by Anonymous Coward · · Score: 0

      In my experience popularity in the technical field very rarely is based on technical merits. See: MySQL, Microsoft, Oracle, PHP, VB, Apache, etc etc etc

  5. god by Anonymous Coward · · Score: 0

    why not just use postgres?

    jeez

    1. Re:god by jellomizer · · Score: 1

      I have. It is just that most people with MySQL deployments or MS SQL deployments just use the Database as a basic CRUD system. So you install it and it let it go. PostgreSQL is a real DB system.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:god by gmack · · Score: 5, Informative

      why not just use postgres?

      jeez

      Ironically, the fact that PostgreSQL is a better DB makes it easier to convert from PostgreSQL to MySQL than the reverse. MySQL attempts to error correct your SQL queries while PostgreSQL is much more strict. The upshot of this is that queries that works and are tested in MySQL have a good chance of not working and need to be checked (doubly so if the original programmer tried to be clever).

      The company I work for is in the beginnings of a transition. Our PHP and C software have an easy switch to convert between the two databases but now we get to check to make sure every query works and returns the same results in both databases. The cleanup of our queries will be good in the long term but for now it's a LOT of work.

    3. Re: god by montjoy0 · · Score: 2

      Shite? Seriously? Postgres handles data more safely than MySQL. It has less risk of getting taken over by a giant like Oracle. It's fast. It's Free. Are you just trolling or what?

    4. Re:god by jessecurry · · Score: 1

      I made the switch years ago and have never looked back. I was really glad that Heroku adopted Postgres as their standard database and even began providing Postgres as a service (https://postgres.heroku.com), it makes my life easier.

      --
      Those who know, do not speak. Those who speak, do not know. ~Lao Tzu
    5. Re:god by Ash+Vince · · Score: 2

      Ironically, the fact that PostgreSQL is a better DB makes it easier to convert from PostgreSQL to MySQL than the reverse. MySQL attempts to error correct your SQL queries while PostgreSQL is much more strict. The upshot of this is that queries that works and are tested in MySQL have a good chance of not working and need to be checked (doubly so if the original programmer tried to be clever).

      This doesn't really fit in with the concept of being perfect with what you supply but flexible with what you accept though does it?

      I can understand that Postgres is probably more standards compliant and it is very admirable that it helps you write better SQL by refusing to run badly optimised drivel. The problem with this approach though it is assumes that all developers want to write better SQL.

      Many developers in the world of work don't give too hoots about the quality of the work they produce, they just want go work 9-5 then go home and do other stuff. We might not like it, but there are tons of them, I bet all the people who are working know at least 1 or 2 in their office (If your still at university then they are the guys study CS that hate you for being a geek, unfortunately they don't fail and crawl under a rock). These developers will complain loudly about things "not working" under Postgres and just blame the DB.

      You can argue that Postgres is more standards compliant to management until you are blue in the face, but unless you can demonstrate real world benefits your manager is going to go with MySQL. Sometimes the efficiency of the better queries is a real world benefit, but often that is outweighed by the increased costs of training developers to use postgres (there are fewer postgres devs out there than mysql) since in many situations it is cheap to just throw hardware at a problem. Also the majority of the time efficiency is not really needed since very few people will use the system anyway.

      Technical decision makers will often prefer the tool that is easier to use as the complicated one is probably beyond them. That is why the became managers.

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
    6. Re:god by gmack · · Score: 4, Informative

      The problem is that MySQL only looks easier on the surface. I'm not talking about badly optimized, I'm talking about queries are ambiguous and In many cases where MySQL should return an error it simply returns wrong data. The downside when trying to convert is that in a few cases we have found so far, the original author had simply kept modifying the query until the output until it roughly sent what it was supposed to and the result of that is unmaintainable code that everyone is afraid to touch.

    7. Re:god by tibman · · Score: 1

      That does sound more like developer problem than a mysql one though. You should touch it.. a lot.

      --
      http://soylentnews.org/~tibman
    8. Re:god by gmack · · Score: 1

      I don't disagree with that but there is also a good reason we tend to prefer strongly typed languages: it aids in debugging. Having something error out is much easier to debug than having something return bad data or worse yet: silently corrupt data when writing.

    9. Re:god by tibman · · Score: 1

      So true. There should always be some kind of error or warning. If the developer then chooses to suppress it, that's on them. I do like MySQL errors though. Much more descriptive than the MSSQL ones i get regularly at work.

      --
      http://soylentnews.org/~tibman
  6. In other words by Anonymous Coward · · Score: 2, Interesting

    Oracle is now behaving like Monty's old company MySQL AB, trying to force volume users to pay to play. Remember MySQL AB's rigid enforcement of the GPL, with a dual licensing option? I wonder if MariaDB is subject to the same type of licensing games.

    1. Re:In other words by larry+bagina · · Score: 5, Informative

      MySQL AB could dual-license MySQL because they owned the copyright on the code (outside contributors had to assign their copyrights over). Oracle owns the MySQL copyrights now. MariaDB, as a fork of the GPL code, is only available with a GPL license. He can't relicense it.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    2. Re:In other words by Seumas · · Score: 1

      The future is not in the product my current competition is selling, but in the product I am now personally invested in promoting.

  7. Why "Maria" DB? by roman_mir · · Score: 0, Offtopic

    Why is it named "Maria" DB? She only provided access to herself for money (well, Mary, same thing). Why not "Jesus" DB, at least he saved?

    1. Re:Why "Maria" DB? by SJHillman · · Score: 4, Funny

      Because JesusDB would drop tables for your sins. Perhaps NoahDB would be better. Built-in disaster recovery - it saves just enough data to replicate everything after the disaster is over.

    2. Re:Why "Maria" DB? by sjwt · · Score: 4, Interesting

      I was thinking why not name it OurSQL

      --
      You have 5 Moderator Points!
      Which Helpless Linux zealot/MS basher do you want to mod down today?
    3. Re:Why "Maria" DB? by Anonymous Coward · · Score: 0

      Why is it named "Maria" DB? She only provided access to herself for money (well, Mary, same thing). Why not "RonPaul" DB, for the world's true lord and savior?

      There, fixed that to meet your belief system. You're welcome.

    4. Re:Why "Maria" DB? by Anonymous Coward · · Score: 5, Funny

      NoahDB is not bad, a duplicate record of each kind.

      How about JewDB though? You know it has to be good with business transactions. You definitely don't want a AlQaidaDB, it'll blow up ever so often and the DHS will be on your ass at all times.

    5. Re:Why "Maria" DB? by Anonymous Coward · · Score: 0

      That would have actually been pretty clever.

    6. Re:Why "Maria" DB? by Anonymous Coward · · Score: 2, Interesting

      al-Qaeda already means "the base"
      wiki:
      Experts debate whether or not the al-Qaeda attacks were blowback from the American CIA's "Operation Cyclone" program to help the Afghan mujahideen. Robin Cook, British Foreign Secretary from 1997 to 2001, has written that al-Qaeda and Bin Laden were "a product of a monumental miscalculation by western security agencies", and that "Al-Qaida, literally 'the database', was originally the computer file of the thousands of mujahideen who were recruited and trained with help from the CIA to defeat the Russians."[278]

    7. Re:Why "Maria" DB? by Anonymous Coward · · Score: 1

      NotLarry'sSQL would've been better.

    8. Re:Why "Maria" DB? by nebular · · Score: 1

      "The Base Database"

      Sounds cool in a early nineties BBS kind of way

    9. Re:Why "Maria" DB? by Anonymous Coward · · Score: 0

      Posted AC for fears of retaliation.

      Retaliation for telling lies? What's wrong with that?

    10. Re:Why "Maria" DB? by Anonymous Coward · · Score: 0

      Posted AC for fears of retaliation.

      Retaliation for telling lies? What's wrong with that?

      Did you watch the documentary Sweden's Gender War yet?

      Did you watch the Norwegian documentary "brainwash" (Hjernevask)

      Didn't think so. Don't want you world-view challenged, huh.

    11. Re:Why "Maria" DB? by Flammon · · Score: 4, Informative

      Michael Widenius has two daughters, My and Maria.

      http://en.wikipedia.org/wiki/Michael_Widenius

    12. Re:Why "Maria" DB? by Flammon · · Score: 1

      Oh and a son named Max as well.

      http://en.wikipedia.org/wiki/MaxDB

      Sorry Max, didn't mean to leave you out.

    13. Re:Why "Maria" DB? by Anonymous Coward · · Score: 0

      Because JesusDB would drop tables for your sins. Perhaps NoahDB would be better. Built-in disaster recovery - it saves just enough data to replicate everything after the disaster is over.

      JesusDB will resurrect after 3 days. Though not instant recovery, a complete recovery model without transaction log is a God given, isn't it?

    14. Re:Why "Maria" DB? by Tarlus · · Score: 1

      Because JesusDB would drop tables

      I see what you did there. Brilliant. =)

      --
      /* No Comment */
    15. Re:Why "Maria" DB? by SJHillman · · Score: 1

      So what you're saying is that all your al-Qaeda are belong to us?

    16. Re:Why "Maria" DB? by Anonymous Coward · · Score: 0

      Well, that's it. This is the most clever thing I'll read on the internet today.

    17. Re:Why "Maria" DB? by Anonymous Coward · · Score: 1

      Didn't he have a son - little Bobby Tables?

    18. Re:Why "Maria" DB? by bobdevine · · Score: 1

      > You definitely don't want a AlQaidaDB, it'll blow up ever so often

      The phrase "al quaida" means "the base" or "the database" because it was a list of followers.

    19. Re:Why "Maria" DB? by Cow+Jones · · Score: 1

      Oh and a son named Max as well.

      And MaxDB is a former MySQL AB product (together with SAP AG).

      The domain maxdb.org is now owned by Oracle. maxsql.org is still up for grabs :)

      --

      Ah, arrogance and stupidity, all in the same package. How efficient of you. -- Londo Mollari
    20. Re:Why "Maria" DB? by Cow+Jones · · Score: 1

      Oh dear, please disregard.
      I didn't see the link in your post.

      --

      Ah, arrogance and stupidity, all in the same package. How efficient of you. -- Londo Mollari
  8. So good he wants to sell it twice. by Anonymous Coward · · Score: 2

    Nice dream.

  9. Monty said that? Oh, of course he did... by Richard_at_work · · Score: 5, Informative

    The part he left unsaid was "MariaDB is the future because that's where I will make my money".

    Remember, this is the guy that tried to get a merger court to give him the rights to MySQL back again after he sold them to Sun for a nice sum of money.

  10. Re:Monty said that? Oh, of course he did... by Aardpig · · Score: 1

    Citation?

    --
    Tubal-Cain smokes the white owl.
  11. Me, too! by sidragon.net · · Score: 1

    Because everyone in the open source community has this insufferable "Me, too!" attitude, resulting in half a dozen needlessly duplicative efforts.

    1. Re:Me, too! by Anonymous Coward · · Score: 1

      I meant to respond to the comment asking why we don't just use PostgreSQL, but the point stands.

    2. Re:Me, too! by h4rr4r · · Score: 1

      If we have to select the needlessly duplicative one to ditch, then lets ditch mysql. It is the weaker product.

    3. Re:Me, too! by Anonymous Coward · · Score: 1

      except that you "responded" 3 minutes before the question was asked. Neat trick.

    4. Re:Me, too! by Anonymous Coward · · Score: 3, Funny

      PostgreSQL date handler error?

    5. Re:Me, too! by jellomizer · · Score: 5, Interesting

      Having worked with many different SQL Databases. MySQL, Microsoft SQL, DB2, Informix.... I have found that PostgreSQL is actually a really damn good Database system. Its fast powerful and very configurable. Sure the other guys will have some advantages over PostgreSQL, but I found PostgreSQL has the advantages where I find it counts for my use, for heavy processing, not just storing and retrieving data.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:Me, too! by GameboyRMH · · Score: 2

      You say "needlessly duplicative" like it's a bad thing.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    7. Re:Me, too! by X0563511 · · Score: 2, Interesting

      Can I point existing code at Postgres rather than MySQL and have it work?

      If not, that's kind of a problem.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    8. Re:Me, too! by GGardner · · Score: 1

      Yes, but is that a Postgres problem or a MySQL problem?

    9. Re:Me, too! by i.r.id10t · · Score: 4, Informative

      Depends on what the code is. For example, if you've been using PDO in PHP, then probably no problem, since there is an abstraction layer between your code and the actual SQL calls.

      --
      Don't blame me, I voted for Kodos
    10. Re:Me, too! by rasherbuyer · · Score: 5, Informative

      It's a MySQL problem. Postgres is SQL standards compliant, MySQL isn't.

    11. Re:Me, too! by X0563511 · · Score: 2

      It's a postgres problem - because I'd love to drink the koolaid and use postgres rather than mysql, but you'll note projects that implement specifically against MySQL rather outnumber those that either use postgres specifically or allow you the flexibility to choose.

      I'm not a programmer - I just don't have the skillset. So the chances of my botching it up should I have to manually "port" the various web applications and the like are too high for my liking.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    12. Re:Me, too! by Anonymous Coward · · Score: 5, Insightful

      It's the fault of the users of MySQL for sticking with a non-compliant SQL implementation even when other compliant ones emerged. It's MySQL's fault for not becoming compliant in a manner that encouraged people to take them up on the standards. It's not PostgreSQL's fault that people built to a non-standard.

      And don't even bother making the claim that PostgreSQL should have adopted MySQL's quirks. They had bigger fish to match/fry: SQL Server, Oracle, etc etc. They've actively been working to fix their problems in a standard manner, rather than breaking themselves to match one broken database that very few people actually use outside of simple websites, where it's relatively easy to port to a standard one.

    13. Re:Me, too! by Waffle+Iron · · Score: 5, Funny

      Because everyone in the open source community has this insufferable "Me, too!" attitude, resulting in half a dozen needlessly duplicative efforts.

      That's right. Open source developers should take a cue from the commercial database market: The vendors like IBM, Microsoft and Oracle don't waste resources on duplicate efforts, but instead they collaborate on the one single commercial SQL database engine available on the market today.

    14. Re:Me, too! by Anonymous Coward · · Score: 1

      There's no "kool aid" with postgresql. That doesn't even make sense. "Kool aid" specifically refers to a situation where the "kool aid" peddler has a hidden agenda (typically money or power). Postgresql is 100% free and open source, as well as standards-compliant, with absolutely no strings attached.

    15. Re:Me, too! by Anonymous Coward · · Score: 0

      I never suggested their efforts made sense.

    16. Re:Me, too! by dkleinsc · · Score: 4, Interesting

      What happened was this: Mysql and Postgres got to the point of a usable release at about the same time. Mysql was very slightly easier for someone with a very limited skill set to set up, and was arguably slightly faster, so it quickly became the preference among the crowd that swarmed into "tech" thinking that throwing together some HTML pages was serious programming. This same crowd was also very attracted to PHP because it seemed really simple by comparison to Perl or C for making web pages a bit dynamic. By 2000 or so, it was entrenched as the "LAMP stack", and shared hosting providers were offering Mysql and PHP support as standard (well, sort of standard, with different PHP options available, different versions, etc).

      After the .com implosion in 2001, you had all sorts of people billing themselves as programmers, but only being familiar with PHP and Mysql. Many of them are now working as independent website contractors and the like, and this same crowd is also responsible for writing most of the CMS's out there, which in turn means that they use the Mysql/PHP platform that they know, rather than learn Postgres or Python or Ruby or Java. And that means that Postgres support for CMS's is more often than not an afterthought.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    17. Re:Me, too! by uniquename72 · · Score: 2

      I've never had any problem with any of them. I can also use both a Phillips and a flat-head screwdriver.

    18. Re:Me, too! by X0563511 · · Score: 1

      Great. But instead of picking apart my improper use of an idiom, how about you stay on topic?

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    19. Re:Me, too! by Anonymous Coward · · Score: 1

      MySQL is the Microsoft Windows of databases. Sure, it may be half decent now, but for many years it was clunky, anti-standards, and would modify your data silently. There even used to be a section in the documentation about how bad foreign keys were and why MySQL doesn't have them. MySQL had to be brought kicking and screaming to the basic level that Postgres had already been at for years. I don't trust it to work right. I wouldn't use it if I had to use a database for anything other than a requirement for an existing product (Wordpress and the like).

      I can't fathom why open-source people keep defending MySQL or its forks when they will turn around and knock Windows. MySQL is to MS windows as PostgreSQL is to Linux. Being popular doesn't mean it's better, or we'd all be using Windows and talking about how inferior Linux is.I'd rather have the fast, standards compliant database that's written by developers who value correctness of my data.

    20. Re:Me, too! by Anonymous Coward · · Score: 0

      Huh? You think PostgreSQL is a "me too" project? Are you aware of its history?

      mSQL/MySQL weren't even usable when Postgres started out. There was no guarantee they would get it right or even get it finished, so it was only prudent to develop it in their own desired direction.

    21. Re:Me, too! by Anonymous Coward · · Score: 1

      Slashdot uses MySQL, so maybe that explains it.

    22. Re:Me, too! by znrt · · Score: 1

      you have to be ignorant about mysql, postgreSQL or both. they are as duplicate as a car duplicates a truck. each has it's uses.

    23. Re:Me, too! by h4rr4r · · Score: 1

      I am very familiar with both. Postgres is a great database, MySQL is a damn shame. It simply should not be popular, and proves that marketing and PR are more important than a good product.

    24. Re:Me, too! by Anonymous Coward · · Score: 1

      Both of which are terrible.

    25. Re:Me, too! by Anonymous Coward · · Score: 0

      No, I'm saying the opposite.

    26. Re:Me, too! by Anonymous Coward · · Score: 1

      The code or the SQL? If it's just actual code then, if it was written properly then yes, you should be able to. If it's, say, written in PHP and has used mysql_/mysqli_ functions scattered all throughough then no it can't (and in that case, it wasn't written properly, I would argue).

      The problem with moving from one database to another (regardless of the DB) is that a lot of SQL won't be the same. If it's some little CRUD thing, you probably won't run into a lot (but then, what reason would you have to switch?) But if it's more complicated, you're going to run into a LOT of little annoying SQL differences between various databases. In particular, date functions will greatly vary from DB to DB. Then there are minor things such as referencing full names (one example: SQL Server uses Schema.Owner.Table or Schema..Table (if memory serves, something like that anyways) and MySQL uses Database.Table). There may also be differences in little things like how to escape a keyword. Does it use `table` format or something else? What about other extensions it adds (MySQL has quite a few non standard SSQL functions and such), if you use those you'll need to find equivalents. Finally, how you write stored procedures and functions is likely going to be different.

      Sadly, even if MySQL followed ANSI SQL Standards (it doesn't), there would still be plenty of things that would make it potentially incompatible with just dropping a new database in place. Of course, if you knew this from the start and wrote your code properly, then it's not TOO big of an understaking to make the necessary changes and have the code work for multiple databases.

    27. Re:Me, too! by X0563511 · · Score: 2

      The real problem though is that it isn't MY code, it's some project's code. I have no code, I'm not a coder. I could try to port it, but the chances of be breaking things is significant.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    28. Re:Me, too! by Anonymous Coward · · Score: 0

      "Drinking the kool aid" as used here generally means doing what someone tells you is good for you even though there is either no evidence that is true, or there is evidence that it is not. Since most people who jump into these threads advocating switching to Postgres from MySQL offer no evidence that it is a positive move other than "because I said so," and tend to hand-wave away the fact that such a switch will frequently cause problems in a system which is and has been working quite well, its usage fits well here.

    29. Re:Me, too! by znrt · · Score: 1, Insightful

      all clear: you are ignorant about mysql *and* about carrying out a rational, substantiated argument. (implying your ignorance about postgreSQL, while not proved, is still very likely indeed).

      mysql easily outperforms postgreSQL for small databases. plus, it has tons of native binding libs and allows for bizarre strategies postgresql doesn't, nor does care about. they are two very different approaches to a db engine. if you don't see the differene it's because your use for db engines must be very specific and limited (troll: or because you have no clue altogether).

    30. Re:Me, too! by HornWumpus · · Score: 1

      mySQL was initially DOS, then Windows, then Windows 95/98. Then someone showed them a copy of the ANSI SQL spec. They incorporated it into the 'compliant' version of mySQL aka Windows ME.

      After all that work mySQL is almost as good as Dbase3+.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    31. Re:Me, too! by h4rr4r · · Score: 1, Insightful

      Performance is secondary to your data being there. Also I want to see some evidence of that, I have trouble believing it in 2013.

      I actually admin a fairly large set of Postgres DBs, just so you know smartass.

    32. Re:Me, too! by Anonymous Coward · · Score: 2, Informative

      It's more of a database problem in general. The ANSI SQL Standard isn't broad enough. If the situation was reversed, if you had a project written specifically for PostgreSQL, you wouldn't be able to drop in MySQL, either. Or if the project was written for Oracle, you wouldn't be able to drop in MS SQL Server. As some people have mentioned already, MySQL isn't 100% ANSI SQL compliant. But even if it was, you still couldn't drop it in place more than likely, unless it was a very simple application and didn't use any functionality outside of the ANSI SQL standard.

      AND, even if THAT were true, it would still depend on how it was written. Some languages, like .Net/VB or Perl, force you to use a sort of middle layer in the code. Basically you write code that talks to A database, but not specifically WHICH database. PHP, however, is only just recently adding this sort of functionality. If your project happens to be written in PHP (you didn't say but it's likely given the popularity of PHP) and has been around for awhile, then it's likely that it's written to talk to a SPECIFIC database, and not a database in general.

      This means that even if the databases and the SQL used were perfectly compatible, it STILL wouldn't work because the code is written specifically to talk to MySQL and only MySQL. If this is the case, then the fault wouldn't be EITHER database, but the code (and perhaps to some degree the language used).

      By the way, going based on the number of projects that outnumber one or the other isn't a good indicator. MySQL was pushed as an easy to configure/use sort of thing. A lot of hosting companies sold products based on having a LAMP (Linux, Apache, MySQL, PHP) stack, for example. Thus we have a LOT of projects that are written in PHP and written for MySQL. That doesn't make either better (nor can you infer the opposite). It just means it was marketed really well. It's like saying MS Windows is the best operating system out there because that is what most people use, or that whatever famous pop artist has written the best music ever because they are popular right now (and by comparison, no one listens to classical anymore so it therefore must be junk). Basically, it's a flawed argument.

      Of course, none of that really helps you out because from the sound of your posts you're stuck with MySQL and won't have a choice to move to something else and I suspect that the detailed technically reasons aren't going to be as important to you as that fact. You might, for now, be able to drop in MariaDB as a replacement but that's only because it's a fork and is practically the same database (and for now very specifically tries to be 100% compatible). But give it time and it's likely the projects will drift apart enough that you won't be able to drop one in as a replacement for the other as easily as you'd like.

      In short- a piece of software CAN be written to support multiple database backends, but the software has to be written specifically to do so. And if it is, it would have configuration options to select which database to use. If it doesn't, then it probably can't. And that will be true regardless of what the backend database is.

    33. Re:Me, too! by HiThere · · Score: 1

      For me PostGreSQL, and MySql too, have the disadvantage that you can't have project specific databases. I want the database to be in a file (or directory) under the project, so it's easy to distribute. So that means Firebird, SQLite, H2, HSQLDB, a few others, but *neither* PostGreSQL nor MySQL. Relocating ALL the databases isn't an option, I need it to be project specific.

      What's annoying is that I can't figure out *why* they choose to make this either difficult or impossible. (To be honest, I don't know either of them well enough to say that it's impossible. Just that there's no obvious way to do it, and a simple Google doesn't return any answers.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    34. Re:Me, too! by marnues · · Score: 1

      MySQL has never failed us for data.

    35. Re:Me, too! by Anonymous Coward · · Score: 0

      By calling out the open source community specifically, yes you did suggest that commercial efforts aren't duplicative.

      Say this instead: Because too many programmers have this insufferable "Me, too!" attitude, resulting in half a dozen needlessly duplicative efforts.

      See the difference?

    36. Re:Me, too! by Anonymous Coward · · Score: 0

      For me PostGreSQL, and MySql too, have the disadvantage that you can't have project specific databases. I want the database to be in a file (or directory) under the project, so it's easy to distribute. So that means Firebird, SQLite, H2, HSQLDB, a few others, but *neither* PostGreSQL nor MySQL. Relocating ALL the databases isn't an option, I need it to be project specific.

      So set up an installation that contains just one database and put it wherever you like.

    37. Re:Me, too! by mikeulus · · Score: 1

      Copyleft + Copyright assignment is what's causing some of this. People are hesitant to donate their time to a project if only the other guy can monetize it. I think Apache handles this well by creating a level playing field for their projects. Everyone has ample opportunity to monetize their additions, and so feel more inclined to use and contribute to an existing project. If copyright is as spread out as it is in Linux kernel, then this is less of an issue.

    38. Re:Me, too! by Anonymous Coward · · Score: 0

      Basically because it's a dumb idea. You aren't supposed to ship database binary files around. They are version specific, possibly architecture specific as well.

      You ship some sort of database-agnostic data file around (which probably takes up a lot less space than the actual db files) and ship a script to import it into the deployment machine's database.

      This is really basic stuff.

    39. Re:Me, too! by Kawahee · · Score: 1

      the chances of be breaking things is significant

      This is where unit testing comes into its own.

      --
      I'll subscribe to Slashdot when I see a month without a dupe, a typo, or an article the "editors" didn't read.
    40. Re:Me, too! by Issarlk · · Score: 1

      A DB engine that happilly destroy your data when you change a column's precision is lame, yes. MySQL is a toy.

    41. Re:Me, too! by Dextrously · · Score: 2

      I haven't ever experienced problems with data not being available on MySQL either. Running several Drupal 6 & 7 sites on MySQL. Also, the company I work for hosts their main customer interface against on MySQL and they haven't had any problems in the several years it has been running either.

      Is that an issue from 'ye olde' days? I love your posts, but from what I am reading here, it seems like some have problems with bugs in MySQL that aren't actually there anymore. Either that, or I have just been insanely lucky to not have experienced any of them? I'm running Debian stable with apt sources from (http://packages.dotdeb.org stable). So my MySQL version is 5.5.30-1~dotdeb.0.

      I couldn't blame you in that regard though, once something leaves a sour taste in your mouth, it's hard to find reason to go back and try it again, I've done the same thing. Though this article is definitely inspiring me to have a look at both PostgreSQL and MariaDB. One gripe I had before (in drupal v6 about 2 years ago) was that PostgreSQL was purported to not support a 'distinct' select by the maintainer of the 'views' module (or possibly a random committer?). It made some of the configuration that I tried to do with views not work out correctly, so I ended up hacking the module code to add distinct support.

      Drupal v7 now has a database abstraction layer though, so it now supports specialized queries based on whatever DB you choose to run it on. Drupal 8.. haven't tried it yet, but I looked at some of their DB code using PHP 5.4 traits, and it looks pretty slick. I'm was planning on putting together a new VM soon for testing out Drupal v8 on PHP 5.4, I'll definitely give PostgreSQL and MariaDB a shot.. though http://packages.debian.org/testing/database/ doesn't seem to have a package for MariaDB, looks like mariadb.org has its own repos: https://downloads.mariadb.org/mariadb/repositories/.

      Should be fun!

    42. Re: Me, too! by Anonymous Coward · · Score: 0

      It would still not be meant to move from one location to another. The files are not guaranteed to be in a consistent state and permissions, version differences etc make this impractical.

    43. Re: Me, too! by Anonymous Coward · · Score: 0

      It would still not be meant to move from one location to another. The files are not guaranteed to be in a consistent state

      If they're not guaranteed to be in a consistent state when you move them to a different location then they're not guaranteed to be in a consistent state when you leave them where they are.

      and permissions, version differences etc make this impractical.

      Because there's no way to move or copy a directory tree while preserving its permissions.

      Version (and also platform) differences is a valid point, however.

  12. What's Oracle doing so badly? by CastrTroy · · Score: 5, Interesting

    I would like to know what specifically Oracle is doing so badly. I've been watching MySQL for a while as we use it at work, and it seems that a lot of advancements have been made in MySQL since the Oracle takeover. They've released 5.5 and 5.6. They haven't let it stagnate. They've released a ton of new features. They still have the free version easily available on their website. It seems like their prices have gone up if you want the supported version, but there are other providers out there.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    1. Re:What's Oracle doing so badly? by Xest · · Score: 5, Interesting

      Yeah, I wouldn't use MySQL regardless for anything serious, but I've still played around with it and used it for prototype projects, and frankly the .NET connector and GUI management tools have made far more progress under Oracle than they were making beforehand.

      That's not to defend Oracle either of course, but I think it's unfair to say Oracle has let MySQL stagnate, they haven't, and that's not a reason to ditch MySQL. The fact Oracle are scum and that MySQL is still crap regardless are better reasons to ditch MySQL, but certainly not lack of progress.

    2. Re:What's Oracle doing so badly? by lennier1 · · Score: 1

      For quite some time Oracle couldn't even make a working Windows installer (when it tried to set up the root password and similar stuff you had to kill the installer and complete the last steps manually).

      If a company can't even get a fucking installer to work I certainly don't want to find out which parts of the database engine they managed to break.

    3. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      1. They don't fix bugs in anything like a remotely timely manner.

      2. They are removing functionality with each release.

      3. Their intention is to slowly kill MySQL & InnoDB because this combination is good enough for the majority of database applications, which is killing Oracle in long term. Generic Intel boxen running Linux/BSD with decent RAID are more than adequate to replace the older choice of big Sun/IBM boxen using Oracle's and IBM's weird licensing fees, resulting is IT costing significantly less to buy, license and support.

    4. Re:What's Oracle doing so badly? by gidoca · · Score: 5, Informative

      It's mainly a problem for Linux distributors: they stopped providing things like regression tests and security advisories. Source: https://mailman.archlinux.org/pipermail/arch-dev-public/2013-February/024478.html

    5. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 2, Interesting

      Oracle didn't release patches to fix undisclosed security problems and forced Debian to release a new version of MySQL. Oracle don't work well with distribution package maintainers. Do they expect distributions to release a new vanilla MySQL package every time Oracle says they have fixed some undisclosed problems?

      Due to the non-disclosure of security patch information from Oracle, we are forced to ship an upstream version update of MySQL 5.1. There are several known incompatible changes, which are listed in...

      http://www.debian.org/security/2012/dsa-2429

    6. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      I work for Oracle (not an official spokesperson) and we use MySQL inside a lot of our own products. So we have a desire to see it supported and enhanced.

    7. Re:What's Oracle doing so badly? by CastrTroy · · Score: 2

      I think that MySQL is a great database that suffers from a bad reputation due to a lot of history. Stay away from MyISAM, and it can be a great database. I find it actually does a few key things a lot better than some of their competitors, and you can always start out for free, which is a big advantage for start-ups. Postgres is just about the only other free alternative but has a lot of issues of it's own. Someone pointed out MySQL installer not working, well, if you want to complain about Postgres, how about no case insensitive collation?

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    8. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      You're a fucking idiot and you deserve to be shot.

      - A Linux user

    9. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      lol. MySQL's competition isn't oracle, it's MS Access. There were some .com companies that wasted VC money on sun/oracle when they should have gone linux/postgres (or mysql) but if you're considering oracle, you're not considering mysql.

    10. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      Ha ha, please mod the parent as being funny. A lot of layers to the troll.
      Or he is right ? Windows don't matter .. sniffle/whaaa. Way to ruin my day.

    11. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      Stay away from MyISAM, and it's no faster, and usually slower, than Postgres, which can also handle a lot more load.

      MySQL has a long history of not caring about data integrity. February 31st was a valid date according to MySQL for YEARS.

    12. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      Haha... I sooooo agree with Oracle Installers on Windows. They've been a total joke for years, I'm not sure WTF they were thinking. I'd be at customer sites back with Oracle 8 and you'd have to copy the disk, then use another installer patch since the one on the media was bad (how did they make it past any QA with a non-working installer?!?!?). The installer is "better" today, but it's still not clean, and the default tools they ship with have all kinds of quirks that you get used to where you have to go part-way through, close and start over to get it working.

      Still today they patch like crazy with poor documentation on what changed or why I need that patch, and it feels like Oracle's main product hasn't really improved in any meaningful way for YEARS.

    13. Re:What's Oracle doing so badly? by Xest · · Score: 1

      When I lost faith in it professionally was when I used to use it (was with InnoDB btw) was when a database we'd had running for about 9 months randomly corrupted itself forcing the service to crash and stop.

      I could fix the corrupt files with the command line tools, but it then repeated a few days later.

      The best I could track it down to was a DELETE FROM query it didn't like for some reason (there was nothing particularly special about it) that would arbitrarily cause the corruption.

      I just couldn't justify it's continued use after that. If there's two things I need a database to do it's to not crash and ensure data persistence, if it fails at those things then I can't deem it fit for any kind of production application.

    14. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 1

      Someone deriding someone else for using Windows in defence of MySQL.

      Now that's the definition of irony, if ever there was one.

    15. Re:What's Oracle doing so badly? by OolimPhon · · Score: 4, Informative

      Oracle don't want you to install it. They want you to employ an expensive consultant who knows how to install it.

    16. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      oracle is doing so badly is because oracle is oracle and PEOPLE HATE THEM, including the people that *USED* to work on those projects.. they saw the shit storm coming and they bailed or switched projects...

      losing the long time developers is why oracle couldn't handle openoffice, is why they are dropping the ball on java and java updates, and why they continue fucking up mysql.

      in the case of mysql, it could also partly be a simple conflict of interest... a superior mysql product cuts into oracle db sales... and uncle larry will not stand for that! so they fuck the project up instead.

    17. Re:What's Oracle doing so badly? by Anonymous Coward · · Score: 0

      Stay away from MyISAM, and it can be a great database.

      And complex views and certain subselects and unions that can cause performance to take a huge hit (I forgot exactly what, but there's a case where joining a view to another view in a certain way causes it to completely ignore any indexes). There are also some quirky issues with locking, if I recall, and some lacking when it came to triggers/foreign keys/etc.

      Or, to put another way, Stay away from MyISAM and MySQL can be a great database for CRUD applications. Anything more serious and it can work but it's going to give you nightmares. If I were starting such an application from scratch and absolutely needed a free database, I'd stick with PostgreSQL. Hell, if money were no object, I'd choose SQL Server over MySQL. It's actually a damn good database (and fast, too). Maybe it's because it wasn't originally written by MS but at the very least, they haven't screwed it up yet.

  13. Audio, anyone? by bogaboga · · Score: 1

    Why isn't there an audio of this interview? This should be routine now. While I appreciate efforts to provide this dialogue, I hope the author(s) don't expect that folks will always want to read through all the verbiage.

    I would have been able to listen to the interview while on my way to work. But thanks anyway and sorry, I had to get this off my chest.

    1. Re:Audio, anyone? by rvw · · Score: 1

      Why isn't there an audio of this interview? This should be routine now. While I appreciate efforts to provide this dialogue, I hope the author(s) don't expect that folks will always want to read through all the verbiage.

      I would have been able to listen to the interview while on my way to work. But thanks anyway and sorry, I had to get this off my chest.

      You know, with MariaDB, confessions are still confidential. When this one is sold to Microsoft or Apple, JesusDB will support speech input and output and it can communicate with AngelDB and stuff. Only when goDB will be around, it will answer questions like this itself on slashdot.

    2. Re:Audio, anyone? by radiumsoup · · Score: 1

      because the demand for unedited audio is low enough that it's not usually worth the effort of authors to provide it - and if you include doing voiceovers for the author's own commentary, which generally happens after the interview is complete and the author has the time to verify and rebut statements made by the interviewee, you're talking about a LOT more work than simply putting out a text-based article.

      You could always try text-to-speech.

    3. Re:Audio, anyone? by al.caughey · · Score: 2

      Yeah... my lips get tired too when I have to read a long news article

  14. Ego Check by Anonymous Coward · · Score: 0

    From TFA: "Some of the new code by Oracle is surprisingly good, but unfortunately the quality varies and a notable part needs to be rewritten before we can include it in MariaDB"

    Uh... considering the utter and total lack of quality surrounding MySQL for years (much of it written by this guy), and considering that Oracle has engineered incredibly reliable and extensible enterprise databases, I don't know where the "surprise" comes from. You can hate on Oracle for being evil, and I agree that they are a lot of the time, but you can also bet that they have a whole lot of very smart people who know how to implement a database. Keep in mind, while I don't trust Oracle, they did release all of this code under an open source license for the Maria people to use(or in this case, criticize in the same way the pot criticizes the kettle).

    1. Re:Ego Check by Anonymous Coward · · Score: 0

      They had to.

      Otherwise, MySQL would be dying even faster.

    2. Re:Ego Check by Anonymous Coward · · Score: 0

      Yes. I took a trip one day to the MySQL codebase, and it is incredibly ugly. It was a horror to read it.

    3. Re:Ego Check by Anonymous Coward · · Score: 0

      You can hate on Oracle for being evil, and I agree that they are a lot of the time, but you can also bet that they have a whole lot of very smart people who know how to implement a database.

      This used to be true. Rumor has it that all the smart software developers left Oracle a number of years ago. My perception these days is that the software devs at Oracle couldn't code themselves out of a wet paper bag.

    4. Re:Ego Check by ColdWetDog · · Score: 1

      ... and considering that Oracle has engineered incredibly reliable and extensible enterprise databases...

      You just gave me a hernia. Thanks.

      --
      Faster! Faster! Faster would be better!
  15. Re:Monty said that? Oh, of course he did... by KiloByte · · Score: 3, Interesting

    The part he left unsaid was "MariaDB is the future because that's where I will make my money".

    Except that he put a lot of effort and money into organizing a team of developers for the last four years. Just compare what's going on in Oracle's land vs this fork.

    It's another case of OpenOffice vs LibreOffice.

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  16. why not just use postgres? by rvw · · Score: 5, Informative

    why not just use postgres?

    jeez

    Many providers don't offer this in their cheap standard package. That's a major problem for Postgres I think. Then many popular webapps like Wordpress or Magento are mysql only, and I don't think it will happen soon that they will work with Postgres. Oh and if they did, most of their plugins won't work, so nobody will make the move.

    1. Re:why not just use postgres? by Hal_Porter · · Score: 1

      It's a good decade or so since I've had anything to do with SQL but how can that be true? Is it because people are locked into MySQL's SQL dialect and database format?

      Isn't that an argument for MariaDB which sounds like it should have more or less the same dialect/db format?

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    2. Re:why not just use postgres? by Anonymous Coward · · Score: 2, Interesting

      MariaDB is based on MySQL and tries really hard to maintain binary compatibility with most of MySQL.

      Postgres, while an excellent database, has some differences and thus it might take a bit of extra code for people to adapt to it.

      You're right, though, any properly coded application will have abstracted the data layer so that you can easily port to another database if it's required.

    3. Re:why not just use postgres? by Anonymous Coward · · Score: 1

      Not only that, Postgres isn't as oblivious to your crappy schema decisions... it complains loudly and rightly so.

      Two greatest things to see being used by large players on the web : Python and Postgres.

    4. Re:why not just use postgres? by HaZardman27 · · Score: 2

      any properly coded application will have abstracted the data layer so that you can easily port to another database if it's required.

      Further, many application frameworks give you access to a plugin type system where you can write your queries to one SQL-like format and let the framework translate that into your chosen database's dialect.

      --
      Apparently wizard is not a legitimate career path, so I chose programmer instead.
    5. Re:why not just use postgres? by pspahn · · Score: 1

      Magento is most certainly NOT MySQL only (since 1.6)

      Of course, it definitely IS MySQL only if the developer plastered module setup scripts with SQL code instead of using the ORM that is provided.

      If a module is developed with bad practices, how can you come back and say "Even if Magento did work with Postgres, the module doesn't work with it" when it's the module's fault entirely?

      We spent a good 30-45 minutes discussing non-MySQL options during MagentoU training (the training book specifically mentions MSSQL and Oracle, but there are others),

      --
      Someone flopped a steamer in the gene pool.
    6. Re:why not just use postgres? by Anonymous Coward · · Score: 0

      Right, LINQ for instance will let you do this.

    7. Re:why not just use postgres? by Anonymous Coward · · Score: 0

      Speaking from experience, LINQ works great for hobby projects like building an app for inventorying your record collection. But for building real enterprise apps it's not even in the same league as open source offerings like Postgres + a connector.

    8. Re:why not just use postgres? by Anonymous Coward · · Score: 0

      It really depends how you define "Enterprise software" because it's a completely meaningless term used by people who want to look better than they are.

      Analyze your requirements and figure out if the performance and usability is going to be worth it. If not, don't use LINQ. 99% of the time it will do the job if you spend the time required to optimize it (just like you need to do with your SQL queries).

  17. Actually, it is a success for the GPL. by Anonymous Coward · · Score: 2

    Without the GPL, Mariadb would not exist.

    1. Re:Actually, it is a success for the GPL. by petermgreen · · Score: 1

      IIRC mysql try to claim the GPL applies not just to their client libraries but to any reimpmentation of their protocol. So even if you didn't use their client libraries your software still had to be GPL.

      http://mysqlha.blogspot.co.uk/2010/03/can-protocol-be-gpl.html

      Is that term enforcable? will oracle try to enforce it? I don't know but I do know that it's enough to make me wary of using mySQL or any fork thereof in anything I design in future.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    2. Re:Actually, it is a success for the GPL. by Anonymous Coward · · Score: 0

      Sure it would if MySql used BSD, MIT, LGPL, Apache, etc

  18. Did Oracle even know what they were buying? by CuteSteveJobs · · Score: 1

    Oracles purchased of MySQL never made sense: A popular but very lightweight database? I once used it on an enterprise project and it was too buggy and had terrible locking and reliability problems. If your database is down you're losing lots of money - we lost $50K an hour. InnoDB helped a bit, but in the end we found it MySQL unworkable and moved to PostgreSQL. Oracle is an enterprise company which makes kazillions selling enterprise software to, you know, enterprises. Maybe some ill-informed executive thought they could use MySQL to target the low-end of the market, but eventually realised MySQL just wasn't up to the task and *that* is why they abandoned it.

    1. Re:Did Oracle even know what they were buying? by Richard_at_work · · Score: 2

      Oracle didn't buy Sun for MySQL, it bought it for Java. Everything else was a distraction that it now has to do something with.

    2. Re:Did Oracle even know what they were buying? by Anonymous Coward · · Score: 0

      Everyone knew MySQL's strengths and weaknesses. Oracle bought Sun for Java, Solaris, and SPARC. MySQL came along with the package, and Oracle welcomed the chance to neuter a popular free competitor to their flagship DB.

    3. Re:Did Oracle even know what they were buying? by Anonymous Coward · · Score: 0

      Oracle previously purchased InnoDB, which is the only 'respectable' way to run MySQL.

      I can see the logic from Oracle's perspective. Sometimes smaller LAMP projects take off and become critical infrastructure. It can be difficult to migrate from one rdbms to another. There's an opportunity to sell MySQL support licenses and it gets Oracle's salesmen in the door.

    4. Re:Did Oracle even know what they were buying? by Xest · · Score: 2

      If you were making $50k an hour, is there any reason you were using lightweight databases in the first place when given that income you could've trivially just stumped up for something a bit more reliable like Oracle or MSSQL Server?

    5. Re:Did Oracle even know what they were buying? by RevDisk · · Score: 1

      You're claiming MsSQL is more stable than MySQL? Wow. Uhm. Yea, no. MSSQL has plenty of useful features, mostly being developer friendly. I've used MySQL in enterprise environments, without significant issues. Oracle I'd only consider if I had more money than sense, and felt like burning it for lack of any better ideas.

    6. Re:Did Oracle even know what they were buying? by Xest · · Score: 4, Insightful

      The thing that never ceases to amaze me about Slashdot is that you can say the most uncontroversial thing and there will always be somewhere there to tell you you are wrong. You can say the world isn't flat and there will be someone here to tell you it is.

      You are that guy, the guy telling me the world is flat.

      Really, if you think MySQL is comparable to MSSQL in terms of stability then you really just shouldn't be working with databases at all. MSSQL and MySQL aren't even in the same class.

    7. Re:Did Oracle even know what they were buying? by Anonymous Coward · · Score: 0

      It all depends on what you're doing with it. If you're just storing sales records, or inventory then yeah there's not much difference. You'll never notice the performance / stability shorcomings of MySQL. If you're processing 10k+ transactions / second then it's a different ballgame. At that point the only thing you want is Oracle.

    8. Re:Did Oracle even know what they were buying? by jbolden · · Score: 1

      Any database worth $50k / hr or even $5k / hr should be on Oracle or DB2. MySQL is for databases at the $500 / hr or less.

    9. Re:Did Oracle even know what they were buying? by Anonymous Coward · · Score: 0

      We have hundreds of dedicated MySQL servers, and they run well, and have been for the past decade.
      And only 6 DBAs, it just ain't fair.

      We also have a few MSSQL ones, related to SAP and Exchange and toys like that, so certainly not on our HA money making side.

  19. Re:Monty said that? Oh, of course he did... by Anonymous Coward · · Score: 5, Informative

    I believe he is referring to the efforts to divest the MySQL trademark and copyright from Oracle as a condition of the acquisition of Sun by Oracle by EU courts. Not very nefarious as it was under the assumption that Oracle would destroy MySQLs viability in the future.

    The more interesting part of that whole issue was when you look at how the US pressured the EU court to approve the merger unconditionally.

  20. Cited numbers by gmuslera · · Score: 1

    "Although MySQL is still widely used — Db-engines.com ranks it as the third most popular RDBMS after Oracle and Microsoft SQL Server, compared to MariaDB coming in at #35 — "

    They should had read their methodology before citing them wrong. It is not what is more used (as mysql is basically the default db used by most popular web apps, should be more in the order of popularity of php than in the oracle, like it or not) but what have more active discussion around in certain circles. Even if you think that that measurement "matters" they are talking about "most popular RDBMS" and in the list of RDBMS (not general DBs) MariaDB is #17 (and as mostly transparent replacement of mysql, probably should be in reality between the top 10)

    1. Re:Cited numbers by Anonymous Coward · · Score: 0

      I would have thought that sqlite should be in those numbers.
      It is used on pretty much everything.

  21. Oh! Negative moderation. by Anonymous Coward · · Score: 1

    Rather than actually discuss an obvious failing of open source communities at large--a failing that applies directly to commonly-used databases--let's just suppress the opinion. There ya go!

  22. Where Linux goes - a sign of where the action is? by staalmannen · · Score: 2

    Although (irrespective if we believe the specific numbers or not) ~1% of desktop users are Linux users, I think that 1% is a very significant one containing much of the people doing community contributions to open source projects (either patches or good bug reports). Because of this, I think the fate of the two ex-Sun projects OpenOffice and MySQL is very uncertain, despite having a massively higher user share thanks to MacOSX and Windows users and an established brand. Long-term, I think the developer mind share is more significant and that is obtained by being the default option in various Linux distros.

  23. The obligatory... by Bill_the_Engineer · · Score: 1

    Founder and head of software project claims the future belongs to them. News at 11.

    --
    These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
  24. NoSQL stuff is better for web applications by Gizzmonic · · Score: 1

    Everyone wants Mongo and Redis and all that jazz these days anyway...and quite frankly, they ARE better for web applications.

    I predict MySQL/MariaDB/whatever will slowly fall out of favor in the next few years.

    --
    (-1, Raw and Uncut is the only way to read)
    1. Re:NoSQL stuff is better for web applications by IwantToKeepAnon · · Score: 2
      --
      "Happy families are all alike; every unhappy family is unhappy in its own way." -- Anna Karenina by Leo Tolstoy
    2. Re:NoSQL stuff is better for web applications by sponse · · Score: 2

      Some web applications needs A.C.I.D. transactions. No-relational distributed databases won't replace relational databases until they can do A.C.I.D. transactions. The distributed part is particularly hard for A.C.I.D. transactions, 'cos destroys the performance.

    3. Re:NoSQL stuff is better for web applications by Anonymous Coward · · Score: 0

      Until someone invents a type of math as a replacement for relational algebra, relational databases aren't going anywhere- no matter what all the cool hipster CS grads think. Seriously, what is with the trend from CS grads lately that want to dump decades of proven reliability and experience in favor of the latest greatest fad? NoSQL databases have a use case (largely in all of the places people have used relational databases when they shouldn't have/didn't need to- when there is no need for ACID compliancy or complex relational data at all), but it isn't going to replace all "web applications" anytime soon^H^H^H^Hever.

      Basically, for awhile it seems like everyone decided that it was a good idea for all data to be in a database. So people stuck every kind of data into a relational database. This makes about as much sense as saying you're going to use NoSQL for everything (or that XML is the answer to every conceivable problem- which was another fad for awhile). NoSQL is another tool, but it's only good for what it's good for.

      Seriously, though. Whenever someone invents something new, it seems like people get so excited and want to shoehorn using their new shiny tool into every possible use case. Oh well, we were all young once. Pragmatism isn't something you can teach in school after all. Although a required course on maintaining a 10+ year old code base where assignments are adding features or fixing bugs without screwing up how everything else works about it would be nice. Because that, not writing new code from scratch, is how the real world works most of the time.

  25. What they did was not account for Monty by Excelcia · · Score: 2, Interesting

    The only thing Oracle is doing wrong is thinking that no one could be bold enough to try and sell the same product twice.

    It's a gutsy move. It really is. Sell MySQL to Sun. Claim Sun's purchaser is doing __________ (fill in the blank with whatever evil nasty thing you like) with it. But that's ok, MariaDB will save you from that. Distributions flood to it to get away from the nasty big evil corporation, and suddenly Monty has legally taken back control of what he sold for a cool billion dollars.

    The best part about it, is if Oracle says anything about it, then it just looks like they are trying to trash talk the little guy who is just trying to do the right thing for
    the community.

    And before you think of flaming the idea, remember, Monty is very much the businessman. He almost invented using the GPL as a weapon. He stopped releasing any connector or client licensed as LGPL so he could claim that even using MySQL as a back-end for something else required the entire front-end to be GPLed too - either that or pay him for a commercial license.

    The next company to buy something from Monty better get an iron clad agreement never to fork it.

    1. Re:What they did was not account for Monty by Excelcia · · Score: 1

      And as a follow-up, from the article...

      "MariaDB can only evolve if there are companies that are prepared to either do the development of MariaDB or fund it ... The MariaDB Foundation is ... actively seeking sponsors" Widenius says.

      Wow... Monty is not only taking MySQL back from the company who got it after he sold it, but after getting a billion for it he's now looking for other people to foot the bill.

    2. Re:What they did was not account for Monty by mikeulus · · Score: 1

      The next company to buy something from Monty better get an iron clad agreement never to fork it.

      It's GPL. No such agreement could exist. All of the software up until the point of sale would still be GPL and still be forkable due to the nature of the license. Even given that they retain all copyright, Oracle could change the license upon sale and still not be able to enforce such an agreement because of the terms of previously released code.

    3. Re:What they did was not account for Monty by Anonymous Coward · · Score: 0

      Not all developers are created equal. When purchasing a project from an open source developer, it might be reasonable to ask that in the future he will not contribute to the project or similar projects except under the GPL and a contributer license agreement with the purchasing party. This does not prevent forking per se, but it does prevent the guy who sold his project from starting a new business that sells licenses to the exact same thing.

    4. Re:What they did was not account for Monty by Gorath99 · · Score: 1
      Yeah, Widenius is not exactly occupying the moral high ground here. I just love it when he gives us quotes like these:

      "Why is the price for a MySQL OEM license higher than for Oracle Express?" Widenius asks.

      It's hard to be cheaper than free of charge. And Monty's old company was all about selling licenses. I distinctly remember them trying to scare people into thinking that the GPL meant that no program could so much as connect to MySQL without having to become GPL itself. (This was back when the client libraries were LGPL.) Which of course could be avoided if you bought a commercial license from them. Nevermind that the GPL says no such thing.

      I wonder how dissimilar the world would be, had Monte and Larry's lives been swapped. Maybe not that much.

    5. Re:What they did was not account for Monty by mikeulus · · Score: 1

      They can't sell a license to the exact same thing. When he sold it he sold the copyright which gives Oracle the ability to modify MySQL and sell it as proprietary software. Whoever owns the copyright to the new code contributions to MariaDB will only be able to take the contributions after the fork (ie the sale) and make them proprietary. The only thing that would work is a non-compete agreement, which nobody in their right mind would sign if they want to continue selling software. On the other hand, a billion dollars would probably convince me to retire early.

    6. Re:What they did was not account for Monty by Anonymous Coward · · Score: 0

      Or business 101 get a non compete clause.

    7. Re:What they did was not account for Monty by Anonymous Coward · · Score: 0

      He can't take control of the MariaDB in the way he did with MySQL because Oracle owns the copyrights.

      He will never be able to offer a version that has proprietary bits and sell that. What he sells will be 100% GPL.

      What he should have done is start fresh and actually build something worth using.

      Captcha: reinvent

  26. Because it is. by sidragon.net · · Score: 1

    Yes, it is. In this case, we have two different projects that are both hard at work on inventing the wheel. We all know exactly how we want the wheel to work, but because we're dividing our efforts we're getting two wheels that work very similarly, and aren't truly interchangeable.

    A SQL database is meant to store and retrieve data in a very specific way, and do those tasks as quickly and reliably as possible. The mathematics that define how best to accomplish these goals is a common factor. So why the hell do we have two independent projects chasing those goals?

    You tell me: what is the benefit? (And don't start spouting terms "monoculture," because that's baloney. This isn't a biological ecosystem we're talking about here, and even if you use that term, Apache proved it wasn't a problem a long time ago.)

    1. Re:Because it is. by GameboyRMH · · Score: 5, Insightful

      It gives you two slightly different wheels to choose from, that's a good thing. Apparently some people feel like working on different wheels.

      And if monocultures aren't a problem than what's with all this Windows malware?

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    2. Re:Because it is. by Max_W · · Score: 1

      +1 (Where are the moderator points, when you need them?)

    3. Re:Because it is. by Vancorps · · Score: 5, Insightful

      Okay, then MySQL should go away since PostgreSQL was here first and did it right from the start.

      If you look at the development of MySQL over the years its been a long waiting game of features that should be prevalent in any proper DBMS system but the lead developers openly admit they were not database guys when they started out so it's not really any wonder that the product was lacking from the very beginning and still shows its weakness today.

      So the benefit is that you have a good product that you can rely on and it happens to be free. For MySQL you have a mediocre product with broad deployment because it relied so heavily on programmers to do in the application what normal databases handle for the programmer. This usually makes programmers happy as they think they know data management. So with MySQL a programmer must also know how best to handle data management, with PostgreSQL you have proper data management built right in. The database server does work rather than just being a storage repository with the MySQL approach.

    4. Re:Because it is. by Anonymous Coward · · Score: 0

      Neither one turns as well as it should, because those people can only work so much. And there is a good chance they are both on your car at once, and you can't easily change them out to be the same, and they require entirely different equipment to maintain or even mount.

    5. Re:Because it is. by Anonymous Coward · · Score: 0

      Could you give some examples of what data management tasks the programmer has to do that the MySQL database doesn't do?

    6. Re:Because it is. by Anonymous Coward · · Score: 2, Interesting

      If you look at the development of MySQL over the years its been a long waiting game of features that should be prevalent in any proper DBMS system but the lead developers openly admit they were not database guys when they started out so it's not really any wonder that the product was lacking from the very beginning and still shows its weakness today.

      People are thinking about MySQL and Postgres incorrectly. Someone explained the situation in the following way that made things much clearer for me:

      Postgres is a (relational) database. MySQL is a datastore/backend for you web app. Postgres could be used for web apps or for actual database use cases. MySQL should properly be used only for the former.

      MySQL (except perhaps in recent years) was/is not an actual database. It may look like a database, but it is not (or was not, until recently).

      If you only have one set of code (e.g., your web app) accessing your MySQL instance, then as long as your code is relatively clean, it's not a problem. Once you have multiple sets of code, and need proper server-side enforcement of schemas, then Postgres is the one that does this properly. MySQL can finally do this in recent releases if you jump through enough hoops of different settings, but by default it does not do this, and so is not a proper database.

      It is people thinking that MySQL is a "proper" database when it was/is not (e.g., ACID, enforcing schemas by default) the reason the debate arises. MySQL is a great backend for web sites—but that does not make it a general purpose database. It makes it a generic datastore.

      MySQL can be made to act like a RDMS, but most people don't change the setting to use it that way. Postgres on the other hand come set up that way out of the box and you have jump through hoops to force it to NOT act like RDMS.

      So feel free to use MySQL to solve whatever problems you have, but please don't call it a database unless you're running it without at least the following settings in the my.cnf:

      default-storage-engine = innodb
      sql-mode= \
      "STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER"

    7. Re:Because it is. by snadrus · · Score: 1

      "developers open admit they were not database guys when they started"
      And how were they supposed to be, by working at Oracle first? Oracle's DB wasn't made by guys experienced with Oracle when they started.

      "do in the application" .... "data management"
      What is it you're saying it lacks?

      "database server does work"
      Stored procedures & triggers are a nightmare for upgrading software, because you must take a DB offline or carefully delete triggers on upgrade of the app using it. It is this way because this way works better.

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
  27. What about FireBirdSQL? by Anonymous Coward · · Score: 0

    It seems nobody here has mentioned firbirdsql as a nice replacement, its license lets you use it on commercial products is pretty versatile.
    You can access database in the typical client/server way or embedded (more similar to sqlite)

    Anyone that requires a RDBM should check it out: http://www.firebirdsql.org/

  28. Re:Where Linux goes - a sign of where the action i by Anonymous Coward · · Score: 0

    so OpenOffice and MySQL are withering on the vine, while LibreOffice and MariaSQL are moving forward nicely.

    similar to what happened with xfree86 and X.ORG.

    If your project is run by a bunch of jerks that don't listen to the community, no surprise when they go over your head, fork the program, and leave you in the dust.

  29. Re:Monty said that? Oh, of course he did... by Anonymous Coward · · Score: 0

    So Monty with a dozen old cronies versus 200 plus developers under Oracle mgmt. Monty makes better FUD than code.

  30. Not One Link to the Actual Project Page by Anonymous Coward · · Score: 0

    Seriously, how do you post an article about a software project, INTERVIEWING THE CREATOR, and not have one god damned link to the actual homepage or the software?

    https://mariadb.org

    Why did I have to google that? Why were there 20+ irrelevant links in the opening paragraphs of the article? Why wasn't the actual website even mentioned until paragraph 7 of the second section? WHY didn't they even link it? Really? Gee, thanks, Rohan Pearce. Wouldn't want to enable my laziness, right?

  31. Re:Monty said that? Oh, of course he did... by Anonymous Coward · · Score: 0

    Personal blog? As a source?

  32. How much did he make selling MySQL to Sun, again ? by Anonymous Coward · · Score: 0

    Easy to whine after you've sold the shop.

  33. Re:Monty said that? Oh, of course he did... by Anonymous Coward · · Score: 0

    I love how these literally have "monty says" in the url

  34. Monoculture. by sidragon.net · · Score: 1

    Because Windows is shit? Of course, Windows is quite secure these days. I already answered your point by referencing Apache HTTPD. Try again, maybe?

    Again, you're using a term from an entirely different sphere that describes a phenomenon among biological organisms. Software products don't have variation from copy to copy, they don't breed, and they don't evolve through natural selection. They're designed and modified in response to specific needs and threats. Nothing could be further from how living things survive and propagate.

    1. Re:Monoculture. by GameboyRMH · · Score: 2

      Well then call it not putting all your eggs in one basket if you like.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
  35. MySQL's creater is a douche by WaffleMonster · · Score: 0

    You have the right to be a sellout all you want its a free country. Just don't flush your integrity down the toilet while concurrently expecting others to still give a shit about you.

    If I had to choose from one of the open source relational databases it would be PostgresSQL anyway.

  36. LAMP? by Anonymous Coward · · Score: 0

    Are there plans of replacing MySQL with this in LAMP/XAMP?

    1. Re:LAMP? by ArcadeMan · · Score: 1

      If you replace MySQL with MariaDB, you get LAMP instead of LAMP.

      Oh, wait...

  37. Re:Monty said that? Oh, of course he did... by Richard_at_work · · Score: 1

    It's his blog. About the best source you can ask for.

  38. Not hard to see this at all by Anonymous Coward · · Score: 0

    Its no stretch to see that companies in the database business want a monopoly as much as people in the operating system business want a monopoly (you can cheerfully overcharge people, and get away with it, and make billions more than a free market should allow). A clear sign that Oracle wanted to do this: when they bought SleepyCat Software (responsible for maintaining the Berkeley DB packages from 1996 to 2006). Does Oracle need the Berkeley DB packages as a product? No. But they cut into some of the low-end market and Oracle didn't want even small-time competition, so they sold it. Likewise they paid US$1Billion for control over MySQL, except that MySQL is dual licensed, and the GPL side needed to fork into MariaDB so that people could still keep using something like it. I understand that Oracle would like to control the small DB market too, but they can't quite get away with that. The US Federal Government was looking over the deal quite carefully (particularly in regards to the Sherman Act). MariaDB is what I have been using for about 18 months. I switched about the time MySQL started using autoconf and automake for builds. I like knowing that the software I'm using will still be legal, in my control, and available, and not cancelled or made non-available by the whims of someone in a board room. I can't bet my business on that, and I won't.

  39. Re:Monty said that? Oh, of course he did... by Anonymous Coward · · Score: 1

    It's Monty's personal blog. What more do you want? You won't get a better source of Monty's own words than Monty's blog with his own words that he wrote. It's the very definition of a primary source.

  40. Couldn't you find a less biased source? by MouseTheLuckyDog · · Score: 1

    Like say Florian Meuller?

  41. Re:Monty said that? Oh, of course he did... by Anonymous Coward · · Score: 0

    Personal blog? As a source?

    The personal blog of the person who is accused plainly talking about what he was accused of doing. Or is a personal account of one's own behavior not a valid source?

  42. Cabaret by Anonymous Coward · · Score: 0

    Did the headline godwin this thead befor it even began?

    "The future belongs to me" is a song the Nazis sing in the musical "Cabaret."

  43. Serializing a MySQL database by Anonymous Coward · · Score: 1

    That is a good use-case for sqlite, and I often use sqlite for similar reasons, but you could do something similar with MySQL's mysqldump and mysqlimport commands.

    You would serialize your live MySQL instance to a file with mysqldump, ship that file with your project, and then the end-user would bring up their own live MySQL instance and deserialize the file into that instance with mysqlimport.

    The reason you can't just copy around a MySQL or PostgreSQL file and use it directly like you can sqlite, is that these databases possess "process" components http://en.wikipedia.org/wiki/Process_%28computing%29 as well as "file" components. Sqlite relies on the program accessing the data to provide the "process" for running the software that accesses the sqlite file. It's a pretty significant architectural difference between them.

    This means, among other things, that MySQL and PostgreSQL can be run on a central computer, which other computers access over the network, and sqlite cannot (unless you export sqlite via a sufficiently POSIX-compliant network filesystem, but most network filesystems do not provide all the support necessary to allow concurrency-safe sqlite access).

    1. Re:Serializing a MySQL database by HiThere · · Score: 1

      OK. "process" components seems a decent reason for the design, even though it's not something I'd use. (I'd thought they only stored source code, not processes.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  44. Dumb Name by poison1701 · · Score: 1

    Who the hell would name their product MariaDB?