Slashdot Mirror


MySQL Founders Reunite To Form SkySQL

mikejuk writes "The founders of the original MySQL, the open-source database, are getting back together in a merger between Monty Program and SkySQL. SkySQL was created by around two dozen former MySQL executives and investors after Oracle bought MySQL from Sun. Widenius started Monty Program AB and created the MariaDB database from some of MySQL's open source code. The merger will provide a stronger rival to MySQL, so reassuring users who are worried about Oracle's future plans for the database."

215 comments

  1. Executives and investors by Anonymous Coward · · Score: 0

    That's all I needed to hear.

  2. What a relief by verifine · · Score: 4, Interesting

    Anything that takes Oracle out of the way of MySQL gets my vote!

    1. Re:What a relief by cayenne8 · · Score: 5, Interesting

      Why don't they all throw themselves in with PostgreSQL, which is more of a real robust relational database, and continue that as the true open source alternative to Oracle?

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    2. Re:What a relief by Dresden+Sparrow · · Score: 1

      Postgres is great. More of a "product" than MySQL. And options/choices are good. So I am glad to see stars align in the open source world. And great name!! I bet it will outclass MySQL in no time!

    3. Re:What a relief by Anonymous Coward · · Score: 1

      Agreed. I'm in a position where I'm forced to use InnoDB on a product and I swear every time I hit one of its myriad idiotic limitations.

      "Oh, your index key prefix can only be 767 bytes long? Well that pretty much craps all over any multi-column index use case with a varchar(255) column *plus any other single column*"

      Admittedly, InnoDB makes MySQL suck *less*, but that's like saying the turd is only 8" long instead of 10".

    4. Re: What a relief by Anonymous Coward · · Score: 0, Offtopic

      MariaDB is a 100% compatible, drop-in replacement for the MySQL database. PostgreSQL is not.

      So on to this same line of thought, does anybody know of a drop-in replacement for Slashdot? I've been here for what seems like 10 years and starting today I can't even login to the site, or use it with my iOS devices.

    5. Re:What a relief by Gothmolly · · Score: 4, Insightful

      Meanwhile, their work allows you to become successful, FOR FREE... so you know, they're definitely screwing you.

      --
      I want to delete my account but Slashdot doesn't allow it.
    6. Re:What a relief by BitZtream · · Score: 2, Insightful

      Yes, ... it'll outclass MySQL in no time ... or rather, negative time, since it has been clearly superior to MySQL for years in every way. The only thing that keeps MySQL popular is people who don't know what they are doing, which it does fine for.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    7. Re:What a relief by mobby_6kl · · Score: 1

      I'm just hoping they'll try to make a database this time...

    8. Re:What a relief by organgtool · · Score: 2

      You're both right based on different perspectives. The original poster was sympathizing with all of the members of the MySQL community who contributed to the product but received none of the money from the sale. While they were not legally entitled to any of that money, most people considered it very bad form. However, you are correct that the users of MySQL still benefit regardless of who owns the company, but that doesn't do anything to make the actions of the sellers more acceptable.

    9. Re:What a relief by Anonymous Coward · · Score: 1

      Why?

      There's already an excellent Free, Open Source database out there, PostgreSQL.

      So far all they've shown they can to is market shit software to developers who are too fucking lazy to actually learn how to use a real database.

    10. Re:What a relief by Anonymous Coward · · Score: 0

      PSQL is still too slow. While it has improved performance and MySQL has gotten slower with each release (5 is way slower than 4), the two are not even yet in terms of performance. It should tell you something that essentially NO major website uses PostreSQL.

    11. Re:What a relief by Bacon+Bits · · Score: 3, Insightful

      A number of developers familiar with MySQL fire up PostgreSQL or MS SQL Server or Oracle, try it out for awhile, find that they get a ton of errors that they don't understand because MySQL let them get away with egregious idiocy, and then retreat back to MySQL.

      Source: used to be me.

      --
      The road to tyranny has always been paved with claims of necessity.
    12. Re:What a relief by Guspaz · · Score: 1

      I believe BitZtream was referring to MariaDB, not Postgres. MariaDB is a pretty seamless upgrade from MySQL, since it's a fork.

    13. Re:What a relief by Anonymous Coward · · Score: 0

      Monty is the financial backing behind MariaDB and SkySQL and now he merges the two together. Both loosing money.

    14. Re:What a relief by Anonymous Coward · · Score: 0

      Because (1) postgresql is advancing just fine already, and (2) choice is good.

    15. Re:What a relief by Raenex · · Score: 1

      Meanwhile, their work allows you to become successful, FOR FREE...

      Depends on the licensing model. MySQL was notorious for their split-license model to try and extract money from businesses. And really, Monty comes off as a dickhead, so why would I want to license my code or otherwise support him so he could just sell it to some other dickhead again?

      In the meantime, there's PostgreSQL, completely free, no strings attached.

    16. Re:What a relief by Anonymous Coward · · Score: 0

      Why are you so afraid of competition that you (like others before you have for years) suggest that everyone drop mysql for postgre ?

    17. Re:What a relief by Anonymous Coward · · Score: 0

      MySQL has always been a second-rate crap database.

      I used to use it as a litmus test for a company; if they were a MySQL shop then I wasn't interested. I changed that policy one time, boy was that a fucking mistake. Hacks and data integrity problems all over the place to work around the shit database.

    18. Re:What a relief by Bacon+Bits · · Score: 1

      That's beside the point. I was responding to his statement "The only thing that keeps MySQL popular is people who don't know what they are doing, which it does fine for."

      --
      The road to tyranny has always been paved with claims of necessity.
    19. Re:What a relief by Anonymous Coward · · Score: 0

      Why are you so afraid of competition that you (like others before you have for years) suggest that everyone drop mysql for postgre ?

      The short form is Postgres, not Postgre. Postgres was started after the Ingres DB project, and was post-Ingres or Postgres. That eventually lead to being renamed Postgres95, which eventually was renamed to PostgreSQL. The short form nickname though is still Postgres.

      Citation: http://www.postgresql.org/about/history/

  3. Which will power SkyNet by Tablizer · · Score: 3, Funny

    ...Hasta la vista, Baby!

  4. Exciting development for MariaDB by MetalliQaZ · · Score: 5, Informative

    If I understand the release correctly, this will mean that MariaDB will continue with organizational support from SkySQL. Sounds like they are well on the road to being the top MySQL "distribution" which is good reassurance for making the switch.

    --
    "Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
    1. Re:Exciting development for MariaDB by Jane+Q.+Public · · Score: 5, Insightful

      Yes. Especially since it's a "drop in" replacement for MySQL.

      I was already tempted. Now I'm pretty much convinced.

    2. Re:Exciting development for MariaDB by icebike · · Score: 2

      Maybe, maybe not.
      I hope you are right but this is Oracle they are dealing with.

      Now that Widenius has some "Executives and Investors" supporting him, he becomes a target for Oracle lawyers.
      Even without a valid claim, they could tie him up in court for years and years.

      Also remember that Executives and Investors want a ROI, and its hard to do that with an open source project like MariaDB.

      --
      Sig Battery depleted. Reverting to safe mode.
    3. Re:Exciting development for MariaDB by Anonymous Coward · · Score: 2, Insightful

      Also remember that Executives and Investors want a ROI, and its hard to do that with an open source project like MariaDB.

      Erm, you're talking about the people who sold the open source MySQL to Sun for $1BN... They know there's money in open source databases....

    4. Re:Exciting development for MariaDB by icebike · · Score: 1

      Who were they planning on selling it to next, and why should that make me feel all warm and fuzzy about using My/Sky/MariaDB?

      --
      Sig Battery depleted. Reverting to safe mode.
    5. Re:Exciting development for MariaDB by VGPowerlord · · Score: 1

      Erm, you're talking about the people who sold the open source MySQL to Sun for $1BN... They know there's money in open source databases....

      The face that they sold it then turned around and started a direct competitor using its own source code could potentially land them in hot water.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    6. Re:Exciting development for MariaDB by prehistoricman5 · · Score: 1

      That is the beauty of open source - you can do that.

      --
      Fuck Beta
    7. Re:Exciting development for MariaDB by Dareth · · Score: 1

      I want to like it, but if they ever want any real fandom they need to pick a name and stick to it for more than 15 minutes.
      I loved My - S - Q - L and I want to love whatever the hell you call it too!

      --

      I only look human.
      My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
    8. Re:Exciting development for MariaDB by Jane+Q.+Public · · Score: 1

      "Now that Widenius has some "Executives and Investors" supporting him, he becomes a target for Oracle lawyers."

      I don't see why. Open Source projects (and MariaDB is pretty solidly Free & Open Source... I doubt they'd have even the slightest trouble proving that) have long enjoyed corporate support. I don't see that it changes anything.

    9. Re:Exciting development for MariaDB by Anonymous Coward · · Score: 0

      MariaDB is certainly the spiritual successor to MySQL, but that doesn't automatically make it the "best". Percona are doing some awesome work with things like XtraDB Cluster, for example.

    10. Re:Exciting development for MariaDB by Anonymous Coward · · Score: 0

      This is why I don't get companies buying up open source.
      You are paying for the name and nothing else, unless you hire the people working on it.
      I guess they also get the right to close source any future changes they make to it.

    11. Re:Exciting development for MariaDB by Anonymous Coward · · Score: 0
    12. Re:Exciting development for MariaDB by Richard_at_work · · Score: 2

      The real shocker is that Monty tried to get the Sun-Oracle merger court to remove the GPL from MySQL, and allow companies to take the code private, so he could basically pick up where MySQL AB left off before he sold it to Sun in the first place.

    13. Re:Exciting development for MariaDB by BitZtream · · Score: 1

      You're a moron if you think MySQL was the reason Oracle bought Sun.

      Oracle could give a fuck if MySQL exists, you're sadly uninformed if you think MySQL competes with Oracle in anyway. They are not just in different classes, they're at almost complete opposite ends of the spectrum.

      Oracle bought Sun for Java and high end servers. This is clear based on their strategy of you know ... using those things they bought and not discarding them like the crap that Sun had that they see no future in, such as WhateverFreetardOffice is this week and MySQL.

      You don't even know what Sun did, let alone why Oracle would by them.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    14. Re:Exciting development for MariaDB by BitZtream · · Score: 1, Insightful

      Heh, beauty.

      What you call beauty, the rest of the world refers to as a worthless side project, and hence why Oracle dropped work on it.

      You guys think this is a good thing, you're too stupid to realize this is just another example of why a business wants nothing to do with GPL'd software. They can dump a metric fuckton of money into it and then watch the prick who made it walk out the door and take it to someone else and do the same thing.

      You have to be stupid to invest in GPL software.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    15. Re:Exciting development for MariaDB by gmuslera · · Score: 1

      Probably wasn't "the" reason, but was one of the strong ones. Java and Solaris should be the other components, with Solaris maybe being the most strategical ones.

      And yes, MySQL competes against Oracle in what matter most to the company: support contracts. There is a bunch of databases with better features than MySQL, but it have by the market (or at least, as most aren't sales, the users, or the amount of installations).

    16. Re:Exciting development for MariaDB by robmv · · Score: 1

      Because Sun never (that we now of) requested a legal binding of no competition for their purchase of MySQL AB. Sun wasn't bad, ethically, maybe one of the reasons they went under. Oracle on the other hand just got what they got from Sun

    17. Re:Exciting development for MariaDB by gl4ss · · Score: 1

      Who were they planning on selling it to next, and why should that make me feel all warm and fuzzy about using My/Sky/MariaDB?

      what does it matter? anyhow, they're probably getting revenue stream from selling support for it.
      IF they find someone stupid enough to dump millions on them for the _name_ then why not? good luck for finding a sucker like oracle again.

      that would enable them to do r&d and development on it for a while without worrying about ongoing support contracts.

      --
      world was created 5 seconds before this post as it is.
    18. Re:Exciting development for MariaDB by Guspaz · · Score: 1

      Once. They changed the name once. It was MySQL for 14 years, now it's been MariaDB for 4 years. The name isn't changing. SkySQL is the name of the company, not the product.

    19. Re:Exciting development for MariaDB by skegg · · Score: 1

      Dude, if they got a billion dollars they don't need to continue selling it.
      If you created & built-up a business and then sold it for $20 million we could also say "who are you planning on selling it to next".

      Your second question, however, does have merit.

    20. Re:Exciting development for MariaDB by Kidbro · · Score: 1

      Uhm. Read his post again. He didn't mention Oracle. He mentioned selling MySQL to Sun. That was before Oracle got involved. He's talking about how the MySQL founders sold it off to Sun for $1BN.

    21. Re:Exciting development for MariaDB by Paradise+Pete · · Score: 1

      I don't see why. Open Source projects (and MariaDB is pretty solidly Free & Open Source...

      The source code wouldn't be the problem. It depends on what was agreed in the sale. Surely some non-competes were signed. That's nearly automatic for any company buyout. Perhaps they have expired.

    22. Re: Exciting development for MariaDB by Anonymous Coward · · Score: 0

      It was actually Marten Mickos that sold MySQL to Sun for all that money. By that time Monty was just a whiney tag along, like all great coders, they have ideas that go on to become great, perhaps even legendary, but then the majority struggle to remain relevant. How many other big names, well known for a great product went on to do the same again for second time? Sure you can name a few, but look back, how many faded into obscurity, and attempted to launch second and third "innovative ideas" only to be met with public disinterest? Launched on the back of press releases that talk about the product/service being headed up by former founder of .
      For my money, Monty is the worst kind of hypocrite, who sells out for â16,000,000, then spends the rest of his career complaining that, being about the profit is bad, free is good, and the FOSS fans eat it up, not seeing it for the marketing that it is. Sounds like a lot of big musicians, who like to raise awareness for the poor, the hungry, and tell everyone how *we* must help them out, while they continue to wear Gucci, eat caviar, and fly in private jets. If we're lucky we'll see a version of "feed the world" from Monty, with the cast of MariaDB signing backup?

    23. Re:Exciting development for MariaDB by Anonymous Coward · · Score: 0

      Heh, beauty.

      What you call beauty, the rest of the world refers to as a worthless side project, and hence why Oracle dropped work on it.

      You guys think this is a good thing, you're too stupid to realize this is just another example of why a business wants nothing to do with GPL'd software. They can dump a metric fuckton of money into it and then watch the prick who made it walk out the door and take it to someone else and do the same thing.

      You have to be stupid to invest in GPL software.

      Why exactly doesn't that apply to BSD-licenced software as well? GPL haters are always saying "you don't need to insist that derivatives are GPLed, the original free version will always be free", so why can't the seller go back to the original free version and continue to work on it and make money from it? If you're going to say that the buyer can at least keep their modifications closed, they can do that with GPL software as well if they actually bought the copyright.

  5. Stronger rival? by HornWumpus · · Score: 0, Troll

    Are they kidding? These people have already demonstrated their incompetence.

    There are several good open source/free to use database engines. MySQL is not one of them.

    --
    John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    1. Re:Stronger rival? by geek · · Score: 2, Informative

      The majority of the internet would disagree with you. I'm not a big DB person but I do use MySQL on my hosted website. I'd happily go to Postgresql if my provider offered it though.

    2. Re:Stronger rival? by jeffmeden · · Score: 2

      The majority of the internet would disagree with you. I'm not a big DB person but I do use MySQL on my hosted website. I'd happily go to Postgresql if my provider offered it though.

      So many people (99%-ish?) use MySQL as a multi-user sqlite, to organize a few thousand rows for personal sites. And that's great, Mysql is well understood and lived long enough as a fully open source project to be a good choice. But people who use databases for *serious* work (not to devalue anyone's blog, but serious here means many tables of 1M+ rows) there is a vacuum in the open source space since the innovation that used to happen at MySQL is now kept private.

    3. Re:Stronger rival? by HornWumpus · · Score: 0, Troll

      Would you use a bank that kept your account information in MySQL?

      MySQL is only good enough to keep unimportant information. Which means it's not good enough, period. You can never know what will grow into something worth shit. If you built it around MySQL's (and it's bugs) you are stuck with it.

      At best it's a learning tool. Maintain it for a year and you are ether hopeless or you will understand what a good database isn't.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    4. Re:Stronger rival? by geek · · Score: 2

      Understood, but as far as I am aware, MySQL never pretended to be that. I've been aware of MySQL for over a decade and used it off and on. I'm not a DB admin so take what I'm saying with a grain of salt. But MySQL was always the "Use it for your website!" DB package. Facebook seems to get a lot of use from it, granted they use a patched version.

      Postgresql was supposed to be the heavy lifter if I remember right. Is this not the case?

    5. Re:Stronger rival? by shugah · · Score: 1

      Facebook at 13M queries per second would like to say "hi".

      --
      If you aren't part of the solution, then there is good money to be made prolonging the problem
    6. Re:Stronger rival? by geek · · Score: 0

      Facebook seems pretty confident in it. Nearly a billion users. I'd imagine if there was a serious enough issue with it Facebook would end up losing quite a bit of money, more than a bank likely. Granted they have their own patches and forked version but the changes aren't that dramatic that a much smaller business couldn't use it.

    7. Re:Stronger rival? by LordNightwalker · · Score: 3, Funny

      There are several good open source/free to use database engines. MySQL is not one of them.

      On the other hand, it's the only concurrent DB I would consider to be a perfect match for PHP. ;)

      --
      Install windows on my workstation? You crazy? Got any idea how much I paid for the damn thing?
    8. Re:Stronger rival? by MrNemesis · · Score: 2

      Whilst I agree with you (having sweated blood over fixing corrupted MySQL tables more times than I'd care to mention), and wish there was more support for more robust databases, it seems most of the world hasn't caught up with this idea yet.

      Not only do most webhosts only support/provide MySQL (IIRC due to Postgres and others not having quota support), but there's a vast swathe of projects out there that don't have support for anything other than MySQL. Heck, I was looking into upgrading my home install of Gallery only to find out that support for Postgres (or even SQLite) was dropped completely:
      http://codex.galleryproject.org/Gallery3:Requirements

      A similarly disheartening thread from Piwigo can be read here:
      http://piwigo.org/forum/viewtopic.php?id=18008

      Sadly, for a bewildering array of software it's MySQL or nothing. It's partly this monoculture that has, IMHO, contributed to much of the animosity against MySQL, since users are unable to even contemplate trying out something else.

      £0.02

      --
      Moderation Total: -1 Troll, +3 Goat
    9. Re:Stronger rival? by Tarlus · · Score: 1

      But MySQL was always the "Use it for your website!" DB package.

      Hell, it's one quarter of the popular LAMP combo.

      --
      /* No Comment */
    10. Re:Stronger rival? by shugah · · Score: 5, Insightful

      MySQL (or MariaDB, or SkySQL) are not suitable for use in banking, but the vast majority of database applications don't have the same requirements of banks. Banks have extremely high data integrity, retention and security requirements. Armoured cars have extremely high security and cargo integrity and retention requirements. But vast majority of transportation applications don't require armoured cars.

      MySQL is demonstrably scaleable and is secure and robust enough for the vast majority of applications. It is used extensively in health care - which has fairly high privacy and data retention requirements. It's a matter of using the right tool for the right application. Sledge hammers are useful for breaking concrete, not so much for framing. Statements like "because banks don't use MySQL, you shouldn't either" are just ignorant.

      --
      If you aren't part of the solution, then there is good money to be made prolonging the problem
    11. Re:Stronger rival? by shugah · · Score: 1

      To be fair, I think if Facebook were starting over today with a clean codebase, and know they were going to grow into such a massive enterprise, they might have made different design choices. As it is, they are committed to MySQL and have tuned, optimized and tweaked the hell out of it to suite their requirements.

      --
      If you aren't part of the solution, then there is good money to be made prolonging the problem
    12. Re:Stronger rival? by HornWumpus · · Score: 0

      The fact that MySQL is such an incompatible POS that you are stuck with it should prevent anybody from ever starting another new project tied to it.

      Any project that is tied to MySQL was started by incompetents. You are better off avoiding these as they will suck.

      Facebook proves it.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    13. Re:Stronger rival? by Anonymous Coward · · Score: 1

      Diarrhea that sprays all over the toilet bowl at high speed is still shit.

    14. Re:Stronger rival? by NatasRevol · · Score: 2

      But it's high speed!

      --
      There are two types of people in the world: Those who crave closure
    15. Re:Stronger rival? by Anonymous Coward · · Score: 0

      Sorry, I must have missed something, Facebook is actually making money now???

    16. Re:Stronger rival? by geek · · Score: 2

      To be fair, I think if Facebook were starting over today with a clean codebase, and know they were going to grow into such a massive enterprise, they might have made different design choices. As it is, they are committed to MySQL and have tuned, optimized and tweaked the hell out of it to suite their requirements.

      I believe a Facebook engineer once stated exactly what you suggest. I'm sure they would have gone another direction but just the fact that Facebook is able to use it like it does seems to imply it's a pretty capable open source project, despite its flaws.

      In reality, MySQL is sort of a poster child for open source software. It's a case where a company started using it to keep expenses down. Out grew it but because they had the source they were able to modify it for their use and contributed it back to the community. I can't think of a better example really.

    17. Re:Stronger rival? by c0d3g33k · · Score: 3, Informative

      Understood, but as far as I am aware, MySQL never pretended to be that.

      Monty has long made excuses for MySQL's inadequacies (most notably the pre-INNODB argument that foreign key constraints weren't really that important and you could just enforce such constraints in software). So there *were* attempts to pretend that MySQL was a "serious" database equivalent to better alternatives. Many of the shortcuts MySQL uses (or used - some of this is historical) apply to edge cases that aren't apparent to "I'm not a DBA" developers creating simple LAMP applications. But when you *do* run into one of those edge cases, then you quickly feel the pain and realize that it could have all been avoided.

      Here's a good read: http://grimoire.ca/mysql/choose-something-else

    18. Re:Stronger rival? by lgw · · Score: 1

      Facebook at 13M queries per second would like to say "hi".

      Facebook gets that throughput from the sharding system that they wrote - the individual MySQL databases aren't doing anything particularly impressive.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    19. Re:Stronger rival? by Bengie · · Score: 2

      That shit scales horizontally, it must be web-scale.

    20. Re:Stronger rival? by Bengie · · Score: 1

      Facebook uses hundreds of MySQL "servers" and dumb nodes in a load-balanced name-value pair object database.

      Think of using a relation database like a NoSQL DB.

    21. Re:Stronger rival? by geek · · Score: 1

      Thanks for the link

    22. Re:Stronger rival? by felipou · · Score: 2

      Yeah, Wikipedia ain't serious enough.

    23. Re:Stronger rival? by Anonymous Coward · · Score: 0

      MySQL (or MariaDB, or SkySQL) are not suitable for use in banking, but the vast majority of database applications don't have the same requirements of banks.

      You're trying to make a point in favour of MySQL (or MariaDB, or SkySQL), so I hate to contradict. But you really blew it with your opening line. Banks have no more security requirements than anyone else. As proven by their instance on clients using outdated IE only browsers. Any 'appearance' of security by banks is nothing more than theatre for the public.

      Internally, banks have all sorts of rules and regulations to abide by if they want to keep their FDIC eligibility. Many of those R&R are related to security, from physical security to network and computer security. Note: internally. Many of those restrictions don't apply to public interfaces.

    24. Re:Stronger rival? by shugah · · Score: 1

      You're confused. The problem is not MySQL, rather, it's tying an application to ANY specific database. No two databases implement all of the features of a modern relational database in the same way. Transactions, concurrency, prepared statements, stored procedures, referential integrity, mem caching, connection pooling, etc, are all implemented differently and in some cases not at all, and imply database specific limitations on the application. DB Abstraction layers, Object Relational Mapping, code generation/scaffolding, etc. all help, but don't entirely remove the need for regression testing, optimization and even kludges for each different database.

      However there are good reasons to design for a single database. If, as in the case of Facebook, your application will only EVER be hosted in a single environment, it makes no sense to support multiple environments. Facebook doesn't sell an application to the public to be downloaded and hosted at your favourite ISP, they offer a service that is hosted on their own infrastructure.

      If the performance requirements are such that regardless of which database you choose, it would require extensive tuning of both the database and the application, it makes little sense to do this for multiple databases.

      --
      If you aren't part of the solution, then there is good money to be made prolonging the problem
    25. Re:Stronger rival? by shugah · · Score: 1

      Regardless of what database they used, to achieve the scale and performance they require would require similar clustering, memchaching, partitioning, sharding, load balancing, etc. There simply isn't an out-of-the-box database that can scale to this level without resorting to the kind of complexity that facebook has implemented.

      --
      If you aren't part of the solution, then there is good money to be made prolonging the problem
    26. Re:Stronger rival? by lgw · · Score: 1

      I don't think that's quite true - Hadoop works just fine for the analysis backend at Facebook, which stays just as busy. The problem lies with legacy systems written for a RDBMS that could just as easily have been written for a NoSQL DB. If you were starting from scratch today, NoSQL makes a whole lot of sense and scales out-of-the-box quite well - but that's useless to the existing code base.

      All of the major cloud providers have their own version of scale-by-sharding systems for RDBMS, but they're mostly kept internal for now. Give them time to mature and they'll be available as products.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    27. Re:Stronger rival? by Anonymous Coward · · Score: 0

      Yes, but armoured cars are more expensive for instance. What is wrong with PostgreSQL? It's really not enough to say MySQL, MariaDB and SkySQL are good enough, I actually expect it to be better or at least the same as pg otherwise why not just switch over to pg? The resources aimed at forking MySQL are wasted if there is no advantage.

    28. Re:Stronger rival? by monkeyhybrid · · Score: 1

      Facebook has been profitable since 2009.

    29. Re:Stronger rival? by BitZtream · · Score: 1

      If you could get rid of MySQL and PHP, LAMP would be nearly as disappointing.

      Seriously if PHP and MySQL are your flagship products you don't have any clue how disappointing your offering is. If you did, you wouldln't be bragging about them.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    30. Re:Stronger rival? by BitZtream · · Score: 1

      Memcached would like to tell you that MySQL isn't doing shit you think it is doing. Memcached also says 'please to be getting a clue'

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    31. Re:Stronger rival? by BitZtream · · Score: 1

      There are multiple that will do that very thing and in fact have been.

      Facebook is a popular website. Thats where it ends.

      There are multiple out of the box solutions that will in fact work as well as MySQL did 'out of the box' Since they are in no way using Out of the Box MySQL your entire statement is retarded and pointless. You're trying to compare a custom version of some software to an off the shelf generic version and pretend its a fair comparison.

      Its not.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    32. Re:Stronger rival? by BitZtream · · Score: 2

      Its not. Wikipedia's database load is rather low. Serving mostly static content from memcached can be done with any number of databases just as easily.

      Its cute how you guys point out websites with a lot of traffic as if they indicate database load in some direct way.

      Why VISA starts using MySQL for transactions, then you can start talking about it being serious.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    33. Re:Stronger rival? by BitZtream · · Score: 1

      MySQL is only good enough to keep unimportant information.

      Did you not see this line?

      Facebook IS loosing quite a bit of money.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    34. Re:Stronger rival? by BitZtream · · Score: 1

      Yes, we know PHP is crap too.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    35. Re:Stronger rival? by HornWumpus · · Score: 1

      With any decent database you can write ANSI SQL for 99% of the work and never have to touch it again (unless you are going to use a POS like MySQL later).

      There is a world of difference between the changes needed to go from SQL server to Oracle (as you say, stored procedures and other supersets of the ANSI spec) vs going to/from an incompetent implementation like MySQL.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    36. Re:Stronger rival? by Anonymous Coward · · Score: 0

      I noticed that quite a few of the comments here are about MySQL's lack of foreign key constraints (pre-InnoDB). Do the NoSQL databases support foreign key constraints?

    37. Re:Stronger rival? by DrStrangluv · · Score: 1

      You could also call it the poster child for closed source software: a company chose open source because it was cheaper in the short term, and now that they've outgrown it they're stuck devoting countless engineering hours to make the solution work anyway. A closed source system might have cost (a lot) more up front, but may also have required (a lot) fewer engineering resources long term.

      Not that I'm saying this definitively true for the Facebook case study. Rather, my point is we just don't know. Calling this case a poster child for anything is nuts, because we just don't have near enough information. It's funny that everyone keeps bringing Facebook into this at all, being so far from the typical deployment.

      That out of the way, there's really no good reason to use MySQL or it's derivatives any more. Ever. Postgre is superior in pretty much every way. Sure, MySQL is good enough for some things, but that's like saying you'd choose a CRT monitor for your computer when you have a perfectly good LCD right there ready to go. Sure, CRTs still work just fine, but no one in their right mind would choose one over an LCD unless they have some really exotic requirements.

    38. Re:Stronger rival? by c0d3g33k · · Score: 1

      My pleasure.

    39. Re:Stronger rival? by gmuslera · · Score: 1

      Depend on how you define "best". But if market followed the technical best we all would be using. don't know, maybe OS/2 and programming in Ada. As we aren't in that idillic world, we have to deal with what is in use this one. Sometimes you have to live with "good enough for most simple uses", even if are used in environments/ways that are beyond its capacity.

    40. Re:Stronger rival? by Anonymous Coward · · Score: 0

      In the good old days, the P stood for Perl. Which is bad, but not nearly as bad as PHP.

      I much prefer the LNPP (linux + nginx + python + postgres) stack myself, but the nice thing is that you can replace any component save the L for an equivalent and the rest would work just as well.

    41. Re:Stronger rival? by afgam28 · · Score: 1

      I've heard this a lot - this idea that PostgreSQL has better transactional integrity than MySQL, but most applications don't need it, and so they are fine using MySQL instead.

      That's a good reason to not rule out MySQL, but it's not a reason to choose MySQL over PostgreSQL. What exactly are the reasons for choosing
      MySQL/MariaDB/SkySQL over PostgreSQL? I don't know enough about databases to answer this myself, but every time I read about this question, all I hear is "most people don't need PostgreSQL so therefore they shouldn't use it", without much explanation about why PostgreSQL would be worse in any given situation.

      If an armored car had no drawbacks to a normal car, there'd be no reason not to use one for commuting to work. But obviously the drawbacks of armored cars are that they are heavier and use more fuel; what are the drawbacks of using PostgreSQL?

    42. Re:Stronger rival? by raxx7 · · Score: 1

      The real drawbacks of using PostgreSQL: your hosting may not support it, the application you want to use may only support MySQL.

      In the olden days, MySQL was synonymous with using the MyISAM storage engine, which was not very reliable but was faster than the alternatives (the InnoDB storage engine for MySQL or PostgreSQL.
      MySQL+MyISAM was also far easier to setup and configure than MySQL+InnoDB or PostgreSQL.

      And the logic was that for most websites, speed was more important than reliability. There are, however, two problems with that logic.
      Problem 1: Your website may not need full ACID compliance level reliability, but it needs some. It's mighty inconvenient when then system crashes and boots to a corrupted database. It's like when Windows used FAT32 instead of NTFS.

      Problem 2: Nowadays, MyISAM is actually only good at simple, read only, workloads. Complicated queries or writes tend to bog it down. And even simple websites have growing amounts of both.
      Nowadays, InnoDB has improved to the point it is, in general, faster than MyISAM while providing better reliability (and it's finally been made the default MySQL storage).
      PostgreSQL also improved a lot in performance. In particular, it tends to be better at handling complicated queries and at scaling better in multi-CPU systems.

    43. Re:Stronger rival? by greg1104 · · Score: 1

      PostgreSQL has a secure by default stance that can be frustrating the first time you use it. When you start a server, it won't be open to the world and ready to serve queries. You'll have to configure exactly how much access you allow instead. If your only criteria is "which system can I get up and running with the least work?", and a lot of developers fall into that category, you will probably find the strictness of PostgreSQL forces you to do more work. There is a similar strictness with what data can and can't be inserted into the database. If you're using PostgreSQL, you better be ready to distinguish between an empty string and a null value for example. That detail will be important and one you have to manage the implications of. And MySQL will make assumptions to quietly convert data to another type so that your code runs, in many situations where PostgreSQL will force you to eliminate the ambiguity with direct type casting.

      MySQL apps get built faster, but on a non-trivial database you're likely to spend the application's entire lifetime occasionally shaking out weird bugs due to invalid data. PostgreSQL has few easy "let me ignore this right now" shortcuts. You do things by what's considered the right way to the PostgreSQL contributors, which relies on things like the SQL standards for guidance, and that is your only option. If you only care about getting things done now by the quickest and easiest choice, with no regard to the future, you'll use MySQL. To return to the car analogy, are you the sort of person who likes to buy an expensive car now that will likely be reliable for a few years? Or do you want something that costs less up front, but you'll have to pay for service regularly? Some people want to get out the door and driving today with no money down, and that's a MySQL car.

      In addition to integrity issue being likely to introduce bugs, the other downside to always taking the easy way out is that if your application's standards for data integrity go up later, you have nowhere to go. There's a long list of nasty MySQL limitations that are unlikely to ever be resolved. The learning curve for PostgreSQL is something you pay for once, and then benefit from forever.

    44. Re:Stronger rival? by Raenex · · Score: 1

      MySQL (or MariaDB, or SkySQL) are not suitable for use in banking, but the vast majority of database applications don't have the same requirements of banks. [..] MySQL is demonstrably scaleable and is secure and robust enough for the vast majority of applications. It is used extensively in health care - which has fairly high privacy and data retention requirements.

      From what I've seen of healthcare software, it's nowhere near the level of quality you'd expect for such a field. Kind of bizarre that you or anybody else would accept less integrity for healthcare data than a bank.

    45. Re: Stronger rival? by cdwiegand · · Score: 1

      Did Postgres finally join every other database and implement cross-database queries? Call me when they join the new century. My experience with Postgres was that their management interfaces were toe-to-toe as bad as MySql's, no cross database queries, and things like sharding and master-slave had to be implemented in your software.

      --
      . Define sqrt(x) as something really evil like (x / rand()), and bury it deep. Watch your coworkers go nuts.
    46. Re:Stronger rival? by Anonymous Coward · · Score: 0

      Banks should use MUMPs.

    47. Re:Stronger rival? by Rich0 · · Score: 1

      MySQL (or MariaDB, or SkySQL) are not suitable for use in banking, but the vast majority of database applications don't have the same requirements of banks. Banks have extremely high data integrity, retention and security requirements.

      Most people who don't think they don't have all those requirements simply haven't thought of what could happen in the absence of those requirements. It isn't unlike every time I see a poster asking for collections to help out victims of some apartment fire - apartment insurance is fairly cheap and yet many people don't even think about it, despite shelling out almost as much for cable TV as insurance would cost them for a year. People just don't think they need insurance until they do, and then it is too late.

      Think about some database that has been collecting data for years. Now imagine that somebody does some data extraction from it and notices that some of the data looks inconsistent. You investigate and it turns out that under heavy load some records weren't getting stored by your database, or when some application error happens rarely that data is left in an inconsistent intermediate state. This has been happening for years undetected. Presumably if you're storing data for years it has some value, and now that value has been reduced. You might spend hundreds of hours coming up with ways to detect the problematic data and cleaning it up. Now, consider that if you had simply used an ACID-compliant FOSS RDBMS the problem would not have happened at all. Then when you investigate you find that using that database wouldn't have cost you anything more - the programmers simply used what they were more familiar with.

      I'm sure there are cases where performance is more important than data integrity, but the latter should always be considered the priority as a default. Most people just expect computer systems to regurgitate the data that is input into them without error, and they don't think through the consequences of what could go wrong if this doesn't happen.

      Right now I'm frustrated by the lack of Postgres support by FOSS projects. It is really annoying to be stuck with MySQL simply because the average college-age FOSS contributor doesn't understand the value of a database. The whole world runs on databases, and the typical CS program doesn't even talk about them. Sure, I grok the difference between CS and software engineering, but at least a theoretical treatment of the problems that databases solve would imbue graduates with a MUCH better appreciation for their importance.

    48. Re:Stronger rival? by felipou · · Score: 1

      I won't pretend to know exactly how Wikipedia load is distributed, but I'm guessing they have a non-trivial amount of updates, and surely their database isn't small. Sure you can cache everything, but that only solves the static pages served to viewing-only users.

      And if only VISA level is serious, the world must be totally fucking hilarious to you!

    49. Re:Stronger rival? by jeffmeden · · Score: 1

      You can think of the database load at Wikipedia as only being generated by editors. And they have a VERY high ratio of non-editor traffic to actual editor traffic (even counting all the goddamn spam edits). Casually browsing Wikipedia shows you a stream of pages from cache, it is very unlikely that any of your requests actually even touch the database. If "good enough" distributed database systems are all we need then hell, seal up the Mysql code base and call it a day. But Wikipedia (or whatever great, world-changing project comes after it) can't survive for long on stale technology.

    50. Re:Stronger rival? by Anonymous Coward · · Score: 0

      MySQL apps get built faster

      Unless of course you end up spending all your time working around the limit on the number of JOINs you can have in one query, or the unusably slow handling of subqueries, or the rule that you can't use the same temporary table more than once in a query, or the automatic commit when you create a temp table, to name just a few.

    51. Re: Stronger rival? by Anonymous Coward · · Score: 0

      Did Postgres finally join every other database and implement cross-database queries? Call me when they join the new century.

      Call me when MySQL supports more than one database in the first place. (Hint: CREATE DATABASE doesn't do it, it creates a new schema.)

  6. But.. by ltjohhed · · Score: 2

    But Monty doesn't have a daughter named Sky?!

    --
    All generalizations are false
    1. Re:But.. by Alain+Williams · · Score: 2

      Shhh! -- don't tell his wife! :-)

    2. Re:But.. by Anonymous Coward · · Score: 0

      Sky is his gay sex slave.

  7. Skynet by Anonymous Coward · · Score: 0, Funny

    skySQL will be part of the skyNET infrastructure that will kill us all :)

    It's all in the sky.... and clouds....

  8. Maria or Sky by Anonymous Coward · · Score: 0

    So both MariaDB and Sky will coexist, or are the combining?

  9. The crying game by sdinfoserv · · Score: 5, Informative

    Monty needs to stop crying about what Oracle is / will do with MySQL. He sold MySQl walkng away with almost A BILLION DOLLARS! If he cared that much, he wouldn't have sold.

    1. Re:The crying game by phantomfive · · Score: 2

      Is there even a reason to use MySQL as a database anymore? I was under the impression that most people recommend postgresql these days.......

      --
      "First they came for the slanderers and i said nothing."
    2. Re:The crying game by geek · · Score: 4, Informative

      For a billion dollars even a true believer would sell. You could take a fraction of that billion and make another DB and still have enough money to jerk off with thousand dollar bills for the rest of your life.

    3. Re:The crying game by Anonymous Coward · · Score: 1, Informative

      Yes, some of us like Insert performance. You *can* get great performance in PostgreSQL if you use COPY but that is not compatible with ORMs. In my experience, if you use postgres in the magical right way, it works great but if you treat it like you would a MySQL server, it fails miserably. MySQL is very easy to administer and if you know what you're doing it runs well.

      I think postgres is amazing from a developer perspective but they need to fix insert performance and work on clustering a bit more.

    4. Re:The crying game by Anonymous Coward · · Score: 2, Informative

      Most shared hosts provide MySQL, so a lot of web software is coded with MySQL in mind first.

    5. Re:The crying game by Anonymous Coward · · Score: 0

      Only when you in the unfortunate circumstance of wanting to run a certain application, and the programmer who made it decided to only code it for a single database (being mysql).

      I've had to run mysql in a few spots due to that. I migrate back to postgresql immediately as soon as someone adds support of it to the application, or a new application comes along with the feature set we need which supports it.

    6. Re:The crying game by nefus · · Score: 1

      It's called politics and marketing. He's trying to build support for a future product with his left hand while his write hand is playing with the money.

    7. Re:The crying game by Anonymous Coward · · Score: 0

      Ewwww. Paper cuts!

    8. Re:The crying game by Anonymous Coward · · Score: 0

      Why the hell not? If I could sell my brainchild to larry the fuckhead for a billion I'd do that without second thought. AND then fork it, of course.

    9. Re:The crying game by Anonymous Coward · · Score: 1

      Monty = GREED

    10. Re:The crying game by HornWumpus · · Score: 4, Funny

      dev/null has superior insert performance and similar transactional guarantees.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    11. Re:The crying game by Anonymous Coward · · Score: 0

      MyIASM workloads aside, Postgres replication is simply inferior. MySQL 5.6 is fantastic, especially with its parallel replication threads. Postgres has its usage cases, but MySQL is certainly not inferior for most.

    12. Re:The crying game by zachie · · Score: 1

      Usually when a company buys a start-up they make sure a non-compete clause is included in the terms of the acquisition to avoid this. The "make another DB" part, I mean.

    13. Re:The crying game by Anonymous Coward · · Score: 0

      You don't jerk off much then...

    14. Re:The crying game by BitZtream · · Score: 1

      Thats because you're using your MySQL server in a shitty way and arent' aware of the various reasons its shitty.

      Work on clustering ... seriously?

      PostgreSQL has mutli-master clustering built in. A quick check shows that MySQL still has nothing built in for that purpose.

      MySQL fails spectacularly if you use it incorrectly, just like PostgreSQL.

      Your entire post just illustrates your ignorance of both MySQL and other offerings.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    15. Re:The crying game by Anonymous Coward · · Score: 0

      But does it support sharding?

    16. Re:The crying game by shutdown+-p+now · · Score: 1

      It does - and not only it scales in a perfectly linear way, but it's also completely transparent and zero-configuration!

    17. Re:The crying game by Anonymous Coward · · Score: 0

      http://www.mysql.com/downloads/cluster/?product=cluster

      MySQL Clustering. Now you don't have to illustrate your ignorance either.

    18. Re:The crying game by TuxWithoutPants · · Score: 1

      If you still have to jerk off and not have some hot chicks worship you after you have that much money, you're doing it wrong.

    19. Re:The crying game by laptop006 · · Score: 1

      MySQL still has nothing built in for that purpose

      MySQL has had inbuilt multi-master clustering since before PostgreSQL even had master/slave built in.

      --
      /* FUCK - The F-word is here so that you can grep for it */
  10. the latest news from i-programmer.info by nimbius · · Score: 3, Funny

    "general absence of programmers, engineers fails to deter C-levels from merging two companies in an effort to become a more robust alternative to databases that still arent hadoop, couch or hypertable"

    --
    Good people go to bed earlier.
  11. That depends on what kind of user base you want by tepples · · Score: 2

    There are several good open source/free to use database engines. MySQL is not one of them.

    That depends on what kind of user base you want. If you develop a web application for installation on hobbyist web sites, something comparable to WordPress or phpBB or MediaWiki, you need to make it compatible with MySQL because so many budget web hosts provide only MySQL (and possibly SQLite).

    1. Re:That depends on what kind of user base you want by ducomputergeek · · Score: 2

      Then you've not shopped around as there are plenty of budget providers that offer PostgreSQL. I buy and sell vintage & antique furniture from estate sales on the side. Last year I took a break from IT projects, but I did write a simple mobile web app to display my stuff online using jQuery Mobile, Perl, and PostgreSQL using A2Hosting as my provider for like $6 a month.

      This year I'm working on IT projects again. This one just so happens to be based around Wordpress for many reasons. In Q3 this year I've got it in my budget to hire two developers full-time to basically port everything we're using to PostgreSQL. Why? I've dealt with Oracle before. Many times before. And I don't think their corporate culture has changed any, it's just a question of when will they rake you over the coals for MySQL. MariaDB should be a drop in replacement. Should. I've never gone through any major DB change without problems. I'd much rather go to something that I know is stable and pretty well drama free. PostgreSQL offers that right now while the M*SQL community figures out which direction it's going.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    2. Re:That depends on what kind of user base you want by jd · · Score: 1

      Let us say that was true. (It isn't, but let's pretend.) MySQL is faster than PostgreSQL or Ingres, correct?

      Then use PostgreSQL or Ingres for your primary storage DB, and use MySQL to store cached responses. (Key issues, etc, are then a non-issue - you don't need a vast key to identify a cached pre-generated page.) You then get the full power of a complex DB with the performance of a lightweight DB.

      Wait, isn't this what NoSQL databases are used for? Well, duh. Where do you think they got the idea? The rest of the world has been using multi-tier databases for a very long time now, and obviously if you want extremely high performance and only a simple key/value search for your highest-level DB, then why not use a system that is purely key/value?

      The problem with NoSQL databases is that they can be a little TOO simple. You'll often want web pages where -some- of the content is universal, -all- of the content is cacheable, but where different content in some div block is used for different users (or different parameters or whatever). For something programmatic like that, you -could- use a language like Cold Fusion. Which, like its namesake from Utah, has no redeeming value whatsoever. It's much better to do something like this in a database engine rather than in an interpreter running in a servlet inside an interpreter, as procedures can be pre-compiled.

      But if you want to do this, isn't MySQL still heavier than necessary? Oh, lots. What you really want is (NoSQL || (GDBM/QDBM + Network Access)) + Loadable modules. That's about as lightweight as you can get.

      In an "ideal" system, you'd actually have three layers, not two. The lowest level should also be lightweight, but not MySQL lightweight. It wants to load/save data and create views, but having stored procedures on there as well complicates load balancing and high availability. It also means more arcs through the code, and each arc you add is a potential source of bugs. The lowest level wants to be rock steady (though ska will also work), feeding to the servers that do the heavy lifting. That way, database bugs (inevitable, it's complex code) will have no significant impact on transactions, each component in the system is highly specialized (so makes fewer decisions, so is smaller, faster and more reliable), and the critical path of any given transaction is blocked by as few incidentals and overheads as possible.

      Tight coupling of components is only a good idea when components run at roughly the same speed and aren't particularly blocking. The greater the speed disparity or the greater the thread blocking, the more you want loose coupling or complete decoupling. Lacking dynamic reconfiguration, you layer things so that each layer will mostly have just one type of behaviour and the adjoining layers also mostly have just one type of behaviour. There will be exceptions, nothing is optimized for all cases, but if you get most of the available performance under most of the conditions that arise, you're ahead of most of the game.

      The other reason you want multi-tier is for security. Everyone makes mistakes in coding, so you can expect some component of your system to be vulnerable to attack. If it's a component that an attacker cannot reach (because it's effectively firewalled by the databases above it), it's not an issue. If it's a component that an attacker can do nothing with (because all that's being attacked is cached data that will be refreshed from further down after some time interval or when the data below changes), then only those who hit that specific load balancer in the few seconds of significance will see the defaced data. Moments later, the correct data will replace it.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re:That depends on what kind of user base you want by greg1104 · · Score: 1

      Let us say that was true. (It isn't, but let's pretend.) MySQL is faster than PostgreSQL or Ingres, correct? Then use PostgreSQL or Ingres for your primary storage DB, and use MySQL to store cached responses. (Key issues, etc, are then a non-issue - you don't need a vast key to identify a cached pre-generated page.)

      Why use MySQL just to cache responses? People who use PostgreSQL for the backing store just put some memcache-style layer in front for that. That's even faster than MySQL, and you don't have the complexity of a second database to worry about. You can use something very database aware like pgmemcache. Most people pick their cache mechanism based on integration with their application development environment though. On Java use a cache that integrates well with Tomcat+Hibernate+JDBC, etc.

    4. Re:That depends on what kind of user base you want by HornWumpus · · Score: 1

      You have _never_ shipped code!

      Your response makes it obvious.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    5. Re:That depends on what kind of user base you want by jd · · Score: 1

      I've probably shipped more code than you'll run in a lifetime. What's more, it's damn fast code, highly robust and damn-near DDoS-proof. You? Pffft! Your comprehension of systems is only marginally superior to your comprehension of quantum gravity.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    6. Re:That depends on what kind of user base you want by jd · · Score: 1

      I mentioned NoSQL databases (so no marks for observation). The reason for the two layers of RDBMA is that you get a lot of potential blocks by loading everything onto one layer. Worse, you get heavy resource drainage when any serious crunching is done. One system I worked with took 5-6 minutes to complete a particular SQL query and often timed out. I refactored it down to 25 seconds, but that was far longer than I wanted. The tables were huge, swamping the database's caching capacity. The stored procedures were vast, even after refactoring. Intermediate tables were generated by other stored procedures. Moving those intermediate tables and related procedures to a different engine meant they could be fresher without killing the system, and since these tables were now views and not raw tables on the second tier, the security was better. Access times dropped to around 7 seconds.

      So the three tier layout using some permutation of NoSQL/memcache, PostgreSQL and MySQL/MariaDB, for extremely heavy loads, is superior to trying to get one engine to digest everything.

      For very light systems, obviously multi-tier systems are not going to be efficient. Each layer adds latency, and each layer that has excess capability adds latency. You want the lightest system that'll do what you want.

      I started in the late 1980s on gigabyte databases, and they've only grown in size and complexity since then. Back then, I was asked to make the system handle real-time data streams from large gamma ray detector arrays. Which I did. I also managed to show that their network would suffer a meltdown before my software. My approach has been refined, over the years, to include understanding of different topologies (and how to thrash them into submission by writing custom high-performance network protocols), but my personal objective remains the same: there is no way in hell I will let my software suffer a meltdown before your hardware. My software WILL take the punishment you throw at it, give you the results AND complete The Times crossword before you've had time to register that you sent the query at all.

      Because I know I can do this, I have little or no regard for programmers who cannot or will not. Anything I can do, they can do.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    7. Re:That depends on what kind of user base you want by greg1104 · · Score: 1

      I observed that, I just wanted to stop and question your assumptions around why to pull in another database at all. Thank you for answering that clearly.

      If your backend is something as developer oriented as PostgreSQL, are all sorts of interesting but not very well known things you can do there. You can push the difficult cache invalidation issues that always pop up in the top layer directly into triggers. If a piece of work turns out to have larger implications than you want to deal with right there, you can use the LISTEN/NOTIFY interface to kick off asynchronous work. And that work doesn't even necessarily have to happen on the server. Add in the Foreign Data Wrapper feature, and you can farm things out very easily to arbitrary worker nodes, including ones built with other database technologies. Make the worker another PostgreSQL database (presumably optimized for different purposes) with postgres_fdw, and you can even get the information it knows to percolate upward into top level query planning--while low level execution happens elsewhere.

      PostgreSQL has a lot of these interesting features that let you build more complicated architectures. The minute you add another database layer in front of that, you've done something akin to dumbing down the API available. If I build a 3-tier system, it's usually a memcache style layer at top, PostgreSQL as the full featured middle, and something else below there--but under Postgres's control. This is nice from the perspective that until you really need it (when a light system will do) you don't necessarily even need to add the second database into the mix. When it does show up, you can hide it either with FDW or within Postgres's ability to have functions in most popular programming languages, and maybe not even have to tough the top layer to do so.

      Take this philosophy far enough and you can end up with something like Skype's PostgreSQL installation, where exactly how/where the data underneath is stored is done via pl/proxy. Whenever I see people start on the "but PostgreSQL alone will never be fast enough for my web scale app" I ask them if they're more popular than Skype. If not, you can probably ignore using MySQL or NoSQL altogether if you're clever about it.

    8. Re:That depends on what kind of user base you want by HornWumpus · · Score: 1

      More confirmation. jd has _never_ shipped code, doesn't know what DDoS means.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    9. Re:That depends on what kind of user base you want by jd · · Score: 1

      If a network fails before the system, then your system cannot fail in a distributed denial of service attack. Since any decent data centre multipaths, the failure of a network is of no significance.

      Hey, wait! I am a 4 digit UID who has published code since the late 1970s! What the hell do I need to explain to some 6 digit street urchin? Face facts, you are nothing more than semi-evolved slime with the IQ of a desiccated dung beetle. You want to harass an old-timer? You think your pitiful excuse of a right-wing troll is worthy of consideration? Pffft!

      As for your username, Wumpus is probably as intellectual as you can handle. Even a desiccated dung beetle has enough joints to handle the state space.

      We can continue this on alt.flame, assuming you don't confuse that with a URL.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    10. Re:That depends on what kind of user base you want by jd · · Score: 1

      I agree completely with your post. In essence, it boils down to Critical Path Analysis. The fastest a given page or data set can be delivered is equal to the speed of the critical path through the system. When you have heapsloads of parallelism, the critical path can span multiple threads and in some cases be impossible to determine.

      My approach to layering is to simplify the CPA, make responses more deterministic and less vulnerable to accidental deadlocks when related pages are simultaneously accessed. That, alone, speeds things up.

      Yes, PostgreSQL in charge is good, the lowest level is operating as a powerful pre-fetch that can also act as a sanity check to ensure reads don't write.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  12. SQLite by tepples · · Score: 2

    The majority of the internet would disagree with you.

    The majority of Internet users use web applications as a user, not as a server administrator, and definitely not as a developer.

    I'd happily go to Postgresql if my provider offered it though.

    Have you considered SQLite? Some MySQL haters would claim that some of SQLite's features are better even if the concurrency is worse, and if your site is on a plan smaller than a VPS, it probably isn't popular enough to need heavy concurrency yet.

  13. What a relief by Anonymous Coward · · Score: 5, Insightful

    Let's all back these guys so that they can sell us out a second time later down the road, when the community makes them successful again.

  14. Explain, please? by Quirkz · · Score: 1, Funny

    I was just coming around to the idea I might explore MariaDB next time I needed to do something, where normally I've been turning to MySQL. Is SkySQL replacing that, now?

    Also, do any of the large, inexpensive web hosts (hostgator, dreamhost, servint, etc.) provide either of these alternatives yet? Because frankly I'm not going to do a lot of personal configuration or pay a lot extra just for the novelty.

    1. Re:Explain, please? by Anonymous Coward · · Score: 0

      That would be perfect. I mean, what kind of name is MariaDB?
      Would you use MariaDB if your ex-girlfriend or ex-boyfriend was called Maria?

    2. Re:Explain, please? by geek · · Score: 3, Informative

      SkySQL is a commercial entity that uses MySQL and now MariahDB - http://www.skysql.com/

      They are replacing MySQL with MariahDB for their hosted solutions and throwing financial backing at the project. MariahDB is not going away. I would encourage you to look into PostgreSQL however as an alternative: http://www.postgresql.org/

    3. Re:Explain, please? by Quirkz · · Score: 1

      I've heard good things about Posgres from people who should know what they're talking about, but I haven't had anything important or demanding enough to go out of my way to explore it yet. Next time I've got something with any actual business use, I'll probably take a closer look at it. Database stuff isn't part of the day job, so it doesn't come up a lot.

    4. Re:Explain, please? by Anonymous Coward · · Score: 0

      PostgreSQL is excellent. It tends to just work.

      It has excellent performance (especially when you throw multiple clients at it at once, reading and updating) and is very stable. I haven't had it crash on me, except when the underlying SAN went haywire. When the SAN returned, PostgreSQL recovered without issue from its transaction logs and went merrily on.

      Our applications are not that demanding, but we're still averaging 400 transactions per second in a couple of databases with several tables containing many gigabytes in the tenths of millions of rows, 24/7, with several writers and tons of readers working in parallel.

      It's easy to configure, it's completely transactional, it's ACID compliant, it's solid and it's performant.

      YMMV, but we are very happy with it.

      As a bonus, the quality of the source code is outstanding, and the development team is quite disciplined.

      We use MySQL as well, but tend to migrate towards PostgreSQL when possible.

  15. Model for the new FLOSS business model by c0d3g33k · · Score: 5, Interesting

    1. Create a popular but flawed FLOSS product (MySQL).
    2. Build a business atop flawed FLOSS product (MySQL AB).
    3. Ca$h out by selling your baby to formerly glorious tech company on the ropes (FGTCOTR, aka SUN).
    4. Profit!
    5. Leave FGTCOTR after a tasteful waiting period to start your own company DOING THE SAME THING YOU JUST SOLD because you can fork the OSS codebase you just sold.
    6. Take public potshots at EVIL Corp (who very predictably acquired FGTCOTR) for mismanaging the baby you sold (because EVIL), while flogging your fork of the product you sold as a viable alternative (FLOSS, to cloak yourself in the veneer of legitimacy because you can live off of steps 3 and 4).
    7. Reunite to form company that does the same thing the company you sold for big $$$ did, to compete with the product you willingly relinquished control over.
    8. GOTO #1?

    I can't decide whether to admire Monty for successfully gaming the system, or condemn him as an amoral manipulator who wasted no time screwing over the very people he sold out to at the earliest possible opportunity.

    Grudgingly, I lean toward admiration. Nicely done, sir.

    That said, I avoid MySQL as the half-baked relational DB pretender that it is and use PostgreSQL whenever possible. Better technology without the drama. I have never regretted PgSQL once, MySQL many times.

    1. Re:Model for the new FLOSS business model by Anonymous Coward · · Score: 1

      You forgot step 6b - appeal to large government bureaucracy begging them to make an exception to copyright laws to allow you to take back the freedoms that you have already granted that allows you to pull this shit in the first place all because you are selfish bastards.

    2. Re:Model for the new FLOSS business model by BitZtream · · Score: 1

      He's a douche on many levels, but he deserves no credit for this.

      Sun was retarded to buy MySQL in the first place. It was just a fucking stupid thing to do, especially for a billion fucking dollars. They could have had it for free ... instead they gave this douche a billion and HE gets it for free.

      Oracle then proceeded to buy Sun for Java and server hardware. MySQL was never something they cared about. They'll probably be happy if he'd just take it and shut the fuck up. MySQL doesnt' compete in any way with Oracle's target audience.

      Oracle's target audience would laugh if you mentioned MySQL to them. No one in the real database world considers MySQL to be anything more than a shitty networked version of SQLite and in most cases, SQLite is preferred by competent developers to MySQL. MySQL is for Linux fanboys who think LAMP is the singularity of perfection and the only possible way to write websites. They are unaware of the whole universe around them that doesn't suck.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    3. Re:Model for the new FLOSS business model by c0d3g33k · · Score: 1

      I'll agree with you except for the part where they'd be happy if he just took it and STFU. I think Oracle knew exactly what they were doing when they bought Sun, and they cared quite a lot about MySQL. I think Oracle was happy to try and exploit MySQL's popularity as a "gateway drug" - they would be poised and waiting with salespeople to offer a "real database" when folks who built a business on LAMP outgrew it and were looking for something better. To support this opinion, I'll remind you that Oracle bought Sleepycat Software (makers of Berkeley DB) in 2006 directly, not indirectly through a merger. I'd argue that Berkeley DB was the one database that was MORE popular than MySQL for simple web applications. I certainly used BerkeleyDB a hell of a lot, and it was a damned fine tool that didn't try to be more (or pretend to be more) that it was. Still is, IMHO.

    4. Re:Model for the new FLOSS business model by c0d3g33k · · Score: 1

      Damn. Forgot about that. You are absolutely right. Wish I could edit posts.

    5. Re:Model for the new FLOSS business model by Anonymous Coward · · Score: 0

      > who wasted no time screwing over the very people

      He didn't sell it to Oracle. And he didn't sell it to people. Companies have no morale, so IMHO it is only fair to screw them as much as you can. Companies will screw their customers, employers and owners the same way.

    6. Re:Model for the new FLOSS business model by c0d3g33k · · Score: 1

      You're splitting hairs. Companies are run by people. They have or lack the morals the people who run them have.

      Also, Monty announced leaving Sun in Feb 2009 to create his own company. The Oracle merger was completed in Jan 2010. So he conceived of and created his own company to compete with the one he sold to well before Oracle owned MySQL.

    7. Re:Model for the new FLOSS business model by robmv · · Score: 1

      Number 8 will not be possible, because they only have the GPL code, they can't dual license it, unless they replace all code or write a new one from scratch

    8. Re:Model for the new FLOSS business model by greg1104 · · Score: 1

      Here's an edited version, which I wanted to make before sharing it further (thanks!):

      1. Create a popular but flawed FLOSS product (MySQL).
      2. Build a business atop flawed FLOSS product (MySQL AB).
      3. Ca$h out by selling your baby to formerly glorious tech company on the ropes (FGTCOTR, aka Sun).
      4. Profit!
      5. Leave FGTCOTR after a tasteful waiting period to start your own company DOING THE SAME THING YOU JUST SOLD because you can fork the OSS codebase you just sold.
      6. Petition government (the European Commission) to try and prevent EVIL Corp (who very predictably want to acquire FGTCOTR) from acquiring your already sold baby as part of the deal, to make it more expensive for them to acquire.
      7. Take public potshots at EVIL Corp for mismanaging the baby you sold (because EVIL), while flogging your fork of the product you sold as a viable alternative (FLOSS, to cloak yourself in the veneer of legitimacy because you can live off of steps 3 and 4).
      8. Reunite to form company that does the same thing the company you sold for big $$$ did, to compete with the product you willingly relinquished control over.
      9. GOTO #1?

    9. Re:Model for the new FLOSS business model by greg1104 · · Score: 1

      MariaDB is requiring that contributions have their copyright assigned to the latest MontyScamAB or whatever it's called. Monty likes to mess with the licensing on the client side as a way to get leverage on people, and there's already a new client with a messy license history to advance that.

      Eventually they will have enough new code that they can build dual-licensed client or administration add-ons that interface with the GPL center, and then put critical features for non-trivial use cases into those. The last time they ran the add-on scam, they left the backup capabilities in the free version crippled such that you had to buy the Enterprise version to get backup tools that actually worked well. And yet people are falling for every part of this con again, having paid no attention to what happened the last time.

    10. Re:Model for the new FLOSS business model by petteyg359 · · Score: 1

      Except for the stupid legal matter of those people not being held responsible when their company exercises those morals.

  16. I'm sick of the whining. Software development = $ by exabrial · · Score: 1

    Ok honestly, what has Oracle done with MySQL that has been so bad? They've been pretty good stewards. MySQL 5.6 came out and even included full text search for InnoDB. I'm pleased with the product and it's progress.

    This smells like the Jenkins/Hudson gayness... All these projects are forking because of big bad Oracle, before Oracle has even done anything. Good god, the open source community is LUCKY to have a corporation that is willing to sink dollars into an open source project. If that means giving up a little control, I'm cool with that. If they try some bullshit, we can fork it. Stop the friggen whining until then. You cry wolf enough times and the community isn't going to be there when you really do need them.

    So I have a brilliant friggen plan. How about the circle jerk of founders in the SkySQL project go to Oracle and offer and olive branch? There would be rainbows and unicorns and one code base. Wouldn't that be best for the community?

  17. reassure users? by backdoc · · Score: 1

    "The merger will provide a stronger rival to MySQL, so reassuring users who are worried about Oracle's future plans for the database"

    Aren't they the same guys that sold MySQL the first time? How will the new alliance be any more reassuring?

    1. Re:reassure users? by Anonymous Coward · · Score: 0

      Not only did they sell it first time, but they sold it when it was version 5.0, widely regarded as a supremely bad version of MySQL (and one that, sadly, gave it a lot of its reputation to this day). Soon after Sun purchased MySQL AB, they released 5.1. Monty had this to say. A quote: "Don't expect that all critical bugs that you may have encountered in 5.0 to be fixed in 5.1. Even if we have fixed a big majority of the bugs from 5.0 some really critical ones still haven't been addressed."

      To compare with what happened in later years, have a look at Wikipedia's list of milestones and look for patterns. Look, for example, at the mentions of bad or broken features, and see where they are. They congregate around the time MySQL was purchased by Sun. Then they peter out, and in the last few years there is no mention of bad quality and lots of additions of new features

      So, I think it's pretty clear that MySQL has only improved since Monty gave up control, despite the unfortunately entrenched (and somewhat deserved) bad reputation MySQL had at that time and was inherited by Sun. Time will tell if his inverse midas touch continues to destroy his current project.

    2. Re:reassure users? by shutdown+-p+now · · Score: 1

      Aren't they the same guys that sold MySQL the first time? How will the new alliance be any more reassuring?

      It's reassuring because no-one can seriously believe that they'll find another sucker to sell it to for $1B this time.

  18. Soap Opera. by csumpi · · Score: 1, Interesting

    This soap opera is getting way too confusing. Way too much money, way too many project names. In the end, whatever they come up with to circumvent Oracle, they will just sell to the next highest bidder for another billion, then rinse and repeat.

    It seems the only way for us to circumvent all this BS is not to use anything affiliated with Oracle, MySQL, or its creators.

    1. Re:Soap Opera. by VortexCortex · · Score: 1

      I wouldn't go that far, but at the very least look into PostgreSQL and see what it can do -- I mean, doesn't look like it's going to be upended anytime soon.

      Also, this whole mess is what happens when folks settle for non-free binary blobs in their otherwise free & open source software.

    2. Re:Soap Opera. by geek · · Score: 1

      This soap opera is getting way too confusing.

      What else would you expect from a bunch of DBA's?

    3. Re:Soap Opera. by Anonymous Coward · · Score: 0

      Also, this whole mess is what happens when folks settle for non-free binary blobs in their otherwise free & open source software.

      What are you talking about? MySQL is and has been released under GPL for a long time.

    4. Re:Soap Opera. by HiThere · · Score: 1

      The code base is now purely GPL. They no longer own the copyrights, so they don't have a proprietary version to sell.

      OTOH, I really want to avoid having anything to do with Oracle, but I haven't been able to come up with a decent alternative to Java for my current project. I've looked as afar as Scheme (well, Racket), which was almost good enough. I built a small prototype of one section in Ruby, but it was unbearably slow. (Python was a bit better, but not much.) D was a good choice, but it's really deficient in libraries. C and C++ are horrible at handling unicode, garbage collection, MPUs, etc. (Yes, you can do anything in C, but it can take arbitrarily large amounts of code.) Ada was a reasonable choice, except that it's type system was overly constraining. If I had a second choice to the language, it would be Ada, but Java was so much superior that.... well, I know that it's licensed under the GPL, but Oracle has proven so untrustworthy that I'm still hesitant.

      So if I were picking a database, I would NOT choose MySQL. MariaDB at least is a system that Oracle probably can't touch. (Nothing is sure when unethical lawyers are involved, but it's probably true.)

      That said, I really don't like systems that have a global database, and for my purposes an embedded database is probably superior. So I'm currently planning on using H2, though I haven't really decided yet. Since that's Java specific, if I decide that I just can't trust Java, I'll need to switch to another database. For my purposes, though, I really don't need the complexity of SQL. It makes things only slightly better. Perhaps I'll go with Tokyo or Kyoto Cabinet.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    5. Re: Soap Opera. by Anonymous Coward · · Score: 0

      Sure, then when your entire business is based on PostgreSQL, let me know how you get along expanding your team of DBAs from the entire pool of about 200 potential people available, then whittle that down to the ones that have demonstrable PostgreSQL history with a large project that shows that the know their stuff, that'll reduce the potential pool to about a handful, hire one or two and hope to god that he never leaves or gets hit by a truck.

    6. Re: Soap Opera. by Anonymous Coward · · Score: 0

      then whittle that down to the ones that have demonstrable PostgreSQL history with a large project that shows that the know their stuff

      Aside from the general ridiculousness of your post, why should "knowing their stuff" be a requirement when it by definition never was for your MySQL DBAs?

  19. So one might say... by Azure+Flash · · Score: 1

    SkySQL is a sequel to MySQL. Whose sequel? Your sequel? My sequel? SkySQL.

  20. I just love open source by Anonymous Coward · · Score: 0

    Another branch of a product that has already been branched... I can just see where this is going.

    Fan-friggin-tastic.

  21. Re:He sold to Sun, not Oracle by Anonymous Coward · · Score: 2, Insightful

    MySQL was sold to *Sun*, who were good stewards of the code and community. Then Sun was taken over by Oracle.

  22. Re:I'm sick of the whining. Software development = by VortexCortex · · Score: 1

    bad ... good ... pleased ... smells like ... gayness... because ... bad ... Good ... LUCKY ... willing ... means ... little ... cool ... try ... bullshit ... can ... whining ... cry ... community ... really ... need ... brilliant ... circle jerk ... offer ... rainbows ... unicorns ... best ... community?

    Well, that's like, your opinion, man.

  23. Re:I'm sick of the whining. Software development = by shugah · · Score: 4, Interesting

    I think the FOSS community would probably have been fine if MySQL had remained with an independent (and profitable) Sun. But Oracle is not Sun. For me, personally, the Oracle v. Google lawsuit pretty much gave notice that Oracle would go scorched earth on anyone who used "their" open source properties in ways they didn't approve of.

    --
    If you aren't part of the solution, then there is good money to be made prolonging the problem
  24. Stay away by Anonymous Coward · · Score: 5, Insightful

    Because the people who came up with MySQL shouldn't be touching PostgreSQL code.

    1. Re:Stay away by Anonymous Coward · · Score: 0

      oh how right you are ... skydb, from the people who thought foreign keys were an unnecessary, performance-compromising feature!

      i just assumed she/he meant users of the database...

    2. Re:Stay away by Anonymous Coward · · Score: 0

      Wouldn't hurt anything. Its not like anyone uses it.

    3. Re:Stay away by Anonymous Coward · · Score: 0

      Thanks! That comment made my day.

  25. SQL Query by billstewart · · Score: 5, Funny

    SELECT Name, Date, Time, Lat, Long, Photo FROM humans WHERE Name = "Sarah Connor"

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:SQL Query by Anonymous Coward · · Score: 0

      Why get the Name back when you already know what it is?

      SELECT Date, Time, Lat, Long, Photo FROM humans WHERE Name = "Sarah Connor"

      FTFY

    2. Re:SQL Query by Tablizer · · Score: 2

      and world is saved because the data entry person misspelled it "Conor". A toast to human error!

    3. Re:SQL Query by Tablizer · · Score: 1

      Pfffft, newbies. Because there's a 60% chance you eventually give the report to Boss Man* who didn't write the query.

      * or Woman

    4. Re:SQL Query by Anonymous Coward · · Score: 0

      SELECT Name, Date, Time, Lat, Long, Photo FROM humans WHERE Name = "Sarah Connor"; DROP TABLE humans; --"

  26. Do over?? by Anonymous Coward · · Score: 0

    Well, yes, if Facebook could start an organization from scratch with a gazillion dollars in the bank to work with from day one, and a clear definition of what their final product will be, they might have made different design choices. Hell, they might have written their own browser for their own operating system using their own internet.

    But that's not how things work. Facebook can afford to replace MySQL if they determine it's not meeting their business needs today.

  27. Re:http://www.linuxadvocates.com/p/support.html by Dogtanian · · Score: 2, Informative

    I normally mod down both trolls *and* the people stupid enough- or with too little self-control- to be lured into replying to them.

    However, given that at least three ****wits have already modded you "informative" for this post, I feel obliged to point out that the original comment is more than likely a Joe job (as well as a troll), and pretty obvious one.

    Matter of fact, I wouldn't discount the possibility that "your" comment was made by the same person as the original, but the fact it was modded up shows that at least some people believe otherwise.

    Seriously, I can't believe that there are Slashdotters stupid enough to take this crap at face value.

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  28. Wrong Conclusion by andersh · · Score: 1

    The newly merged company will have the two main co-creators of the original MySQL, Monty Widenius head of Monty Program AB, and David Axmark of SkySQL.

    Ulf Michael "Monty" Widenius, is the main author of the original version of the open-source MySQL database and a founding member of the MySQL AB company.

    1. Re:Wrong Conclusion by BitZtream · · Score: 1

      So?

      I've worked at many companies. Rarely are the founders the ones who make the product great. People like Linus are a rare exception, not the norm. Expecting him to recreate his previous impressions is unrealistic at best.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    2. Re:Wrong Conclusion by HiThere · · Score: 1

      He doesn't need to recreate it. What he needs to do is figure out how to build a profitable company around it, now that he only has a GPL codebase (as he sold the other one to Oracle).

      I don't give him good odds, but I also don't think it's impossible.

      P.S.: Yes, the code in the GPL codebase is essentially the same as the code in the non-GPL codebase, but the ways you can legally use it are different.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    3. Re:Wrong Conclusion by cas2000 · · Score: 1

      P.S.: Yes, the code in the GPL codebase is essentially the same as the code in the non-GPL codebase, but the ways you can legally use it are different.

      No, they're not. the GPL does not restrict usage, it only restricts re-distribution - you're only allowed to re-distribute under the same terms as the GPL (i.e. with source or offer for source and with rights to modify, re-use, and re-distribute).

      You can use the code however you like, for whatever purpose you like.

      This "ways you can legally use it" line is the same bullshit that Monty and Mysql AB used to spread when he/they owned the copyright to mysql - he licensed it as GPL and then tried to tell you that you had to buy a commercial license if you wanted to use it commercially. The mysql web site had that crap plastered all over it.

      It was bullshit then, and it's still bullshit now.

      Monty and Mysql AB made a lot of money out of that FUD and he's still got people believing it even now.

      Personally, I think he has demonstrated his lack of ethics and honesty, and find it extremely difficult to believe his claim that he's doing it for the love of the code.

    4. Re:Wrong Conclusion by HiThere · · Score: 1

      Since the way he intends to use it include redistributing it with changes, I stand by my original statement. The MySQL business model depended on being able to license copies of the code with proprietary modifications under a non-GPL license. This business model is now not legally possible.

      While it is true that if you don't distribute the code, the GPL doesn't place any restrictions on your usage, that isn't the state of a database distribution. Now he needs to switch to a model that focuses more on providing consulting services. Some companies have been successful, but it's not a particularly easy path.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  29. Re:I'm sick of the whining. Software development = by Anonymous Coward · · Score: 0

    The main one is holding back security and critical bug fixes. That's a killer in itself. No, MySQL users are not going to migrate to Oracle, ever. Oracle cannot expand their business, and its future is looking very grim as legacy applications on late 90s early '00s Sun boxen are being replaced by significantly faster and cheaper x86 in racks.

    MySQL does not need Oracle, nor does it need a big corp. It is the biggest DB community on the planet, whether you like the DB or not.

  30. We're putting the band back together. by Sir+Realist · · Score: 1

    We're on a mission from God.

  31. Re:http://www.linuxadvocates.com/p/support.html by Dogtanian · · Score: 3, Informative

    He's been posting these emails in almost every thread for the last few days. He's the "my fast pc" spammer for some unknown Linux website. If you check his Contact page [linuxadvocates.com] you'll see I am not him as he doesn't like his email address displayed in a scrape-able way

    Are you really that dim? I already linked "joe job" and you still managed to miss the entire point.

    Let me explain it in *very* *simple* *words*. The person that posted the original "spam" above is probably *not* "Dieter T. Schmitz" as they claim, but someone else who is (a) trying to make him look bad (b) trolling, and/or (c) stirring up trouble by pretending to post spam under his identity.

    Your logic is circular- you're already assuming that "he" posted the original comment, when in fact "he" probably didn't and "he" isn't the same person.

    Good grief...

    He's the "my fast pc" spammer for some unknown Linux website.

    This *does* explain a lot... about you. If you're one of the idiots that genuinely believed the "My Clean PC" comments were spam- even long after anyone with half a brain could see it was being kept going by trolls- then you're even more gullible and blinkered than I thought you were.

    Anyway, I only posted my original comment as a heads up to those so lacking in common sense that they might have planned on harassing the alleged "spammer".

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  32. UHH by Anonymous Coward · · Score: 0

    maybe throwing themselves at mysql they will begin to shit on postgres? this isn't 2001 and mysql is not that far behind.

    1. Re:UHH by cayenne8 · · Score: 1

      this isn't 2001 and mysql is not that far behind.

      Well, you're half right....it isn't 2001.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
  33. Re:I'm sick of the whining. Software development = by BitZtream · · Score: 1

    You have no idea what the term scorched earth means. It in no way applies to what they've done. Stop using words you don't understand just because you heard someone else say it and it sound scary evil to you.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  34. Using SkySQL/MariaDB is for sellouts by BitZtream · · Score: 1

    Thats what they did isn't it? They sold out, then took their toys and left, and are going to do it again.

    Congratulations, you have illustrated to every business in the world who's paying attention why it would be absolutely fucking stupid to invest any money in a GPL project. Your greed has effectively manipulated the concept of FOSS into something more evil than even what Oracle does.

    Oracle is up front about stabbing you in the back. They'll tell you they are going to do it. This prick is just a two faced fuck who will never get support from anyone other than GPL fanboys.

    Anyone with any intelligence is already distancing themselves from this guy, he says one thing while his actions show his intentions are completely different than his words.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    1. Re:Using SkySQL/MariaDB is for sellouts by gl4ss · · Score: 1

      they didn't show that it would be stupid to invest money in a gpl product.

      they just showed that it's a stupid idea to buy a gpl product. investing into it before that was very, very smart from financial point, because someone was stupid enough to buy it for an ungodly amount of money, and for support contract etc. reasons it was probably smart to invest in it even if there hadn't been a sellout - and I don't think he ever made a statement saying otherwise, that he wouldn't ever compete with it after selling and would just jerk off till the end of days. someone wanted to give him a gob of cash and he took it.

      otoh it shows how it can be very useful for the user that the product is gpl.

      --
      world was created 5 seconds before this post as it is.
  35. Re:I'm sick of the whining. Software development = by Tablizer · · Score: 2

    Okay, we'll rework it, but will "asshat" be okay with you?

  36. MyriaskySql? by Tablizer · · Score: 1

    Why does it sound like a Russian word for "diarrhea" when the 3 merge? It would just invite too many "In Soviet Russia" jokes.

    BUT, we need a whackjob name to compete with "Postgresql". In the FOSS world, sounding squishy, green, and crippled is "street cred" (gimp, grep, gnu, lisp, etc.)

  37. Re:I'm sick of the whining. Software development = by gmuslera · · Score: 1

    Maybe this could give you a hint. Looks like a small factor, but is critical for validating whatever you want to do with the code. If is the start of a trend, better to be in a safe zone, i.e. elsewhere.

  38. Re:I'm sick of the whining. Software development = by MTEK · · Score: 1

    Oracle has been good stewards of MySQL. But it's like saying MS has made commendable effort to embrace open standards. Something doesn't feel right. Even at a superficial level, I dunno if it's Larry's desire to own a Hawaiian island while having the look of a Bond villain, or Ballmer -- just being himself -- the mistrust seems justifiable.

    As for SkySQL, I just wish the original band members would go away. I mean, what happened to their billion dollar buyout? Hookers?

  39. Annual hosting contract by tepples · · Score: 1

    Shopping around is fine when establishing a new web site or if the installation of a new application requiring PostgreSQL coincides with the annual renewal of one's hosting plan. For users looking to add your application to an existing web site on a MySQL-only plan, your PostgreSQL-only application is going to lose out to a competitor's application that supports the hosting plan that the site operator has already paid for.

  40. Exotica by tepples · · Score: 1

    That out of the way, there's really no good reason to use MySQL or it's derivatives any more. Ever. Postgre is superior in pretty much every way.

    Other than that PostgreSQL isn't part of the plan that a lot of shared web hosting customers have already bought. Hosting companies tend to consider PostgreSQL itself exotic.

    Sure, CRTs still work just fine, but no one in their right mind would choose one over an LCD unless they have some really exotic requirements.

    Light guns are "exotic". Zero lag in games is "exotic". Shared web hosting is also "exotic".

  41. Known quantity by tepples · · Score: 1

    I actually expect it to be better or at least the same as pg otherwise why not just switch over to pg?

    If you're not starting from scratch, MySQL or whatever it becomes is better because migrating your existing MySQL based application is easier.

  42. Re:I'm sick of the whining. Software development = by HiThere · · Score: 1

    Sorry, but Oracle and MySQL are playing to different audiences. The number of Oracle database customers is a lot smaller than the number of MySQL users, but I doubt that you could justly claim that less money is involved, and it's the money that Oracle (the company) cares about.

    That said, though the MySQL community has the largest number of users, that's not at all the same as the largest number of active database program developers. I'd need some evidence for any claim that the MySQL project has more active developers than any particular other project (and I doubt that the evidence is publicly available). OTOH, I will agree that the number of active developers is less significant than the quality of those developers, and the quality of the management of those developers. Perhaps this article is evidence of an attempt to improve the MySQL project's management of the developers. (I'm not convinced that it's evidence of movement in the direction of improvement, but it may well be evidence of an attempt at movement in the direction of improvement.)

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  43. You forgot a piece by Anonymous Coward · · Score: 0

    ; DROP TABLE humans; --

  44. very bad form is really a bit of an understatement by Anonymous Coward · · Score: 0

    I remember reading something on slashdot about a nullo ?

  45. Re:I'm sick of the whining. Software development = by Anonymous Coward · · Score: 0

    So, as far as I can tell he's just using "scorched earth" to basically mean "apeshit." Seems fine to me. Is there a more specific meaning of "scorched earth" in this context of which I was previously unaware?

  46. Re:I'm sick of the whining. Software development = by shugah · · Score: 1

    Scorched earth means to destroy (burn) the land to deny your opponent the ability to sustain his army in the field. I used the term exactly as I intended; to suggest that Oracle is more than willing to destroy Java (or at the very least chill independent innovation) in order to win a hopeless IP battle against Google.

    --
    If you aren't part of the solution, then there is good money to be made prolonging the problem
  47. Re:I'm sick of the whining. Software development = by shugah · · Score: 1

    Let me spell it out for the learning impaired. Scorched earth means to destroy the environment to win a battle by denying an opponent the environment needed to sustain his army. It's a strategy that has been used notably by Russia vs Napoleon and by the Soviets vs.Germany. You could also categorize the US Agent Orange tactics in Vietnam / Cambodia as scorched earth.

    By attempting to exert patents and copyright protections to not only Sun/Oracle's Java implementation but to the language itself (interface specifications) Oracle was more than willing to destroy the community that made Java successful in order to win a battle with Google. In the end they lost the battle and, at the very least, made the Java community even more wary.

    --
    If you aren't part of the solution, then there is good money to be made prolonging the problem