Slashdot Mirror


Monty Wants To Save MySQL

An anonymous reader writes "It seems as if the MySQL author is trying hard to win back control over MySQL. In his blog he calls upon the MySQL users to 'Help keep the Internet free' by signing his petition. He fears that if Oracle buys Sun they automatically get MySQL which would spell doom for the project. But I have have mixed feelings with this call for help, because after all — who sold MySQL in the first place?"

371 comments

  1. yay by Anonymous Coward · · Score: 4, Funny

    ...First at last

    For the sake of topic titles, I'd rather if Monty saved Python.

  2. well... by buanzo · · Score: 3, Insightful

    we still have pgsql, right? yeah, migration, but still free/libre, right? first post? nah...

    --
    Buanzo Consulting - 15 Years of GNU/Linux experience, for you.
    1. Re:well... by Chatterton · · Score: 2, Informative

      Not anymore since version 8 in my book. You must check and compare the last versions to make your mind again.

    2. Re:well... by LS1+Brains · · Score: 2, Informative

      I agree - PG v8 is the stuff awesome is made from. Slightly more confusing for non-techies to set up and get going, but still not exactly difficult - and nothing a quick start guide doesn't solve.

      Migrating your typical apps from MySQL to PgSQL can take a bit of effort, but it definitely isn't difficult.

    3. Re:well... by Anonymous Coward · · Score: 0

      Exactly what is it that makes postgres suck?
      Please enlighten us.

    4. Re:well... by pmontra · · Score: 2, Insightful

      The P of LAMP used to by PHP. When did it change to Python and did something happened to Apache while I wasn't looking?

    5. Re:well... by Anonymous Coward · · Score: 1, Insightful

      What the fuck are you talking about? Monty isn't involved with Microsoft or their Codeplex site.

      Also, Python has never traditionally been part of the "LAMP" stack. The "P" stands for PHP.

      Finally, the LAMP stack has been on its way out for some time now. These days, most new sites developed by sensible developers are built on FLPP (FreeBSD/Lighttpd/PostgreSQL/Python) or FNPP (FreeBSD/Nginx/PostgreSQL/Python) stacks.

    6. Re:well... by poetmatt · · Score: 2, Insightful

      I thought it was PHP/Python, my apologies if I read wrong.

      Apache got screwed in 07, back when this came around.

      What do I mean by this? Well have you noticed how there has been endorsement of the apache license for proprietary software as of late? Basically anything proprietary that is labeled open source will be due to apache license compatibility? That's not to promote apache, that's to dilute it. MS-PL is an easy example of that.

    7. Re:well... by Dan+Ost · · Score: 1

      I don't understand your concern.

      To start using Postgres, you install postgres, initialize the DB, set up the user, verify your code can connect, and you're off. How is that any different or more confusing than MySQL?

      --

      *sigh* back to work...
    8. Re:well... by LS1+Brains · · Score: 1
      lol. Cute attempt to attack my profession. I indeed DO work a tech job, and do quite well with it thank you ;)

      For comparison, and since you mentioned Apple specifically, I have an experience that is quite fresh in my mind. LAST NIGHT I installed Postgresql version 8.4.2-1 on my Macbook Pro. The ENTIRE process took less than three minutes, including the time spent downloading:
      1. Download the pre-built binary package from enterprisedb.com
      2. Make the changes to /etc/sysctl.conf suggested by the installer (increased shared memory)
      3. Reboot
      4. Run the Postgresql installer again, letting it do its thing
      5. Set the admin user/password in the nice installer GUI
      6. Download and install pgadmin3 from pgadmin.org
      7. Fire up pgadmin3 and pop in the username/password specified during the Postgres install
      8. Create my users, databases, tables, etc. as desired

      If this is too complex for you, I humbly submit MySQL may be too tough as well.

    9. Re:well... by shutdown+-p+now · · Score: 3, Interesting

      These days, most new sites developed by sensible developers are built on FLPP (FreeBSD/Lighttpd/PostgreSQL/Python) or FNPP (FreeBSD/Nginx/PostgreSQL/Python) stacks.

      I suspect that LAMP still makes the majority, though, it's just that you've conveniently sneaked up the word "sensible" here, which is of course defined by you as "using the technology I believe to be appropriate".

      Meanwhile, the mention of FreeBSD there already makes me go "huh?". Not even to mention non-Apache web servers, and Python over PHP (I wholeheartedly wish PHP to die a quick death, but at this point, for web development at least, it is clearly more popular than Python by any measure).

    10. Re:well... by TheRealMindChild · · Score: 1

      It's a database server. Since when has a "non-techie" needed one of those, let alone there is no sanity in letting a "non-techie" maintain a database server?

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    11. Re:well... by Ash+Vince · · Score: 1, Flamebait

      Migrating your typical apps from MySQL to PgSQL can take a bit of effort, but it definitely isn't difficult.

      Are you insane? In the current economic climate finding time to make a coffee is difficult.

      In order to stay in business you have had to be damn lean recently. For a lean business finding the time to rewrite legacy applications is almost impossible as you have to concentrate on work that will bring in money and hence pay wages. Some legacy applications however might be reasonably mission critical and hence need continued security patches coming from upstream to the underlying database. There are going to be a lot of companies who built large web based applications on the LAMP stack and now have to try and find a way to recode a system for a different DB when they should be doing paid work.

      Ok, maybe it will be a year or so before Oracle can screw MySQL into the ground, but that is still not very much time if you already have 6 months of booked in paid work. Normally you might be able to borrow money to fund an expansion of the development team, but you go to a bank as a small business and try and get some cash? If you do not have a house to offer up as security they are not interested, and who wants to put their house on the line. If MySQL does get bought by Oracle we can only hope that the recovery is in full swing before the ill effects of the takeover take hold.

      The other issue here that currently SUN hold various patents covering MySQL for defensive purposes. This might cause substantial problems if an attempt was made to fork the project. I am not a lawyer so have no idea the extent of this issue, but just the uncertainty regarding this may put larger organisations from sponsoring a fork of the MySQL project.

      Maybe then we will be able to call it the LAPP stack, but that is a long way off. In the mean time I would much rather see Oracle forced to sell MySQL or spin it off as a separate company as a condition of the purchase of SUN.

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
    12. Re:well... by tuxgeek · · Score: 1

      Choice is always good
      It's just the right time to fork mysql to keep it free and going

      --
      "Suppose you were an idiot...and suppose you were a member of Congress...but I repeat myself." Mark Twain
    13. Re:well... by hibiki_r · · Score: 3, Informative

      The main difference IIRC is that you actually have to enable postmaster to take connections, instead of being locked down by default. I'm glad it's locked by default myself, but there's people that don't want to read any documentation.

      Postgres is a freaking enterprise database. Its documentation is so good, it makes every other framework in my development stack look bad. But people complain because they'd rather have the easy things be trivial, without caring about the difficulty of the not so easy things.

      We also run MySQL at work, and we have a whole lot more problems with it. The developers, who were the ones that chose MySQL in the first place, are considering a switch to Postgres, based on how fewer headaches we get with our Postgres installations.

    14. Re:well... by Ecuador · · Score: 2, Informative

      Actually, the P in Lamp is supposed to be "Perl/PHP/Python". And yeah, Perl has seen better times.
      As for Apache being destroyed by being touched by MS... what a slashdot thing to say! ;)

      --
      Violence is the last refuge of the incompetent. Polar Scope Align for iOS
    15. Re:well... by Mad+Merlin · · Score: 1

      Have things changed? Last time I tried Postgres (7.4), the default permissions were extremely liberal. IIRC, full read/write for all accounts on all databases, no passwords, and listening on all interfaces. Freaked me out until I fixed it.

    16. Re:well... by Mad+Merlin · · Score: 1

      The P has always been PHP/Perl/Python.

    17. Re:well... by LS1+Brains · · Score: 1

      For legacy apps, why bother recoding at all? Legacy usually means "we're done with it, we deploy with a set/tested configuration with no new development scheduled." What prevents us from continuing to use existing MySQL v3.x through v5.x deployments into any foreseeable future? Nothing I can think of, so the legacy apps should be safe from a licensing/ownership standpoint.

      For new/continuing development on existing apps, should the MySQL climate turn poor, converting your query syntax from MySQL to Postgres is quite trivial. The libraries to connect your apps are obviously also readily available. Unless you've REALLY tied your app to MySQL-specific options which cannot be easily duplicated, it shouldn't take long at all to get the queries changed and the app into Q/A testing.

      While I agree the prospect of extra work in today's world could be upsetting, I don't believe the challenges involved with conversion to Postgres are nearly as difficult as some fear - or at least they haven't been for the ones I've done. I also don't think we need to panic about the MySQL situation quite yet either. In short, take a couple hours to play with Postgres and determine for yourself whether it makes sense for anything you're working with. I'm guessing many folks would be pleasantly surprised if they haven't looked at it for a while.

    18. Re:well... by orasio · · Score: 1

      hmmmmmm
      Postgres is a bid harder than Mysql, to install and configure.
      As a developer, though, PostgreSQL is beautiful.

    19. Re:well... by sirlark · · Score: 2, Interesting

      Seems to depend very much on distro. Ubuntu karmic allows local only connection by username/database name only... gentoo allows full trust to all local connection to all databases. Don't know offhand what the compiled from source outside of package management scenario is, but a quick visit to pg_hba.conf and the comment in the file explain it all. edit, restart and go

    20. Re:well... by sirlark · · Score: 1

      and I seem to have completely lost the ability to form the plural of the word 'connection' in English... I love my painkillers :)

    21. Re:well... by Hognoxious · · Score: 1

      You'd be surprised. MythTV uses it, for example.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    22. Re:well... by SanityInAnarchy · · Score: 1

      It doesn't matter how shiny and nice it is under the hood, if things are more complex than they should necessarily be.

      I'd argue just the opposite. Say you're on shared hosting -- it's now your hosting provider's responsibility to admin the database. So you really don't care how difficult it is for them, you care how well the thing runs under the hood.

      If you're on a VPS or a dedicated server, and you're managing it yourself, you've already made things more complicated than it needs to be.

      There's a reason why everything Apple makes is so huge a success: Simplicity.

      "Everything"? Enjoying your Apple Newton, I presume?

      Techies and non-techies a like use them for that sake, despite it sucking completely as a phone.

      Ok, first of all: Not everyone even likes the iPhone. Sorry to burst your Reality Distortion Field there, but it's true.

      But if you're right, and Simplicity Is God, explain why every truly "visual" programming language ever has failed utterly? Even "Visual Basic" isn't -- it's still text under the hood.

      The reason is simple: Power. I can do things in a few lines of text that'd take twenty clicks of drag-and-drop, and my text will be more maintainable, more readable, and easier for tools like version control to work with.

      So, sorry, but the usability by non-techies of a database is right down there with the usability by non-techies of a programming language. To take your words, if you can't RTFM (or, worst case, buy a book) and figure it out yourself,

      i really hope you aren't working a tech job, perhaps a store clerk would be more suitable.

      Now, if Postgres was needlessly complex, I'd agree with you. If it can be made simpler while keeping the same feature set, sure, go for it -- it's open source, there's nothing stopping you.

      But since people here are arguing that it's better than MySQL, it still makes sense. Yes, simple is good when I want to expose my Postgres app to users, but they won't be typing sql commands or admin-ing the database.

      --
      Don't thank God, thank a doctor!
    23. Re:well... by Anonymous Coward · · Score: 0

      No but we do have Firebird which is similar in features to pg but performs way better. In fact, Firebird is a like combination of MySQL (performance) and PostgreSQL (features).

    24. Re:well... by Unequivocal · · Score: 1

      You are mixing apples and oranges, I think.

      You are arguing that Apache, the webserver is screwed, because Apache the Foundation is supported by Microsoft.

      Apache the webserver continues to do what it's done for about 15 years. Serve web requests via an open framework. Nothing has changed, so LAMP is still the same inre the "A"

      You and I probably disagree as to whether the Apache Foundation is still doing good work, but that's got very little to do with the Apache webserver's viability.

    25. Re:well... by bytesex · · Score: 1

      Unless you come up with some concrete examples of your difficulties, you're FUDding. Call me distrustful, but I think you're just FUDding.

      --
      Religion is what happens when nature strikes and groupthink goes wrong.
    26. Re:well... by poetmatt · · Score: 1

      nah, I agree with you that apache does good work, but it doesn't speak well for the foundation and/or does indeed fall in line with traditional microsoft methods of subverting something they dont' like.

      So different, apache itself isn't bad, but MS trying to subvert it = everyone has their eyes on where it could potentially go.

    27. Re:well... by Seq · · Score: 1

      I thought it was Perl!

      --
      -- Seq
    28. Re:well... by JThaddeus · · Score: 2, Interesting

      We've been happy with Firebird. A few years ago, I was looking to port some 40K lines of Embedded SQL from Oracle to an open source database. MySQL had fees for commercial use, and at that time PostgreSQL lacked the transaction management we required (it may now, but it certainly did not then). The port to Firebird 1.5 when smoothly, and subsequent upgrades a have been painless. It's simple to install, simple to manage.

      --
      "Love is a familiar; Love is a devil: there is no evil angel but Love." --William Shakespeare ('Love's Labors Lost')
    29. Re:well... by aztracker1 · · Score: 1

      You obviously haven't read the MS-PL have you? It's basically a BSD-like license with a nuclear (patent) deterrent clause.

      --
      Michael J. Ryan - tracker1.info
    30. Re:well... by Anonymous Coward · · Score: 0

      What nonsense. Sensible developers build new sites on LNSR (Linux/Nginx/SQLite3/Ruby) these days.

    31. Re:well... by jonadab · · Score: 1

      > The P of LAMP used to by PHP.

      Actually, I'm pretty sure it's always been Perl.

      Sure, there are variations. Linux/Apache/MySQL/Python, Linux/Apache/mod_perl/Postgres, and a number of others... but the most common expansion has always been Linux/Apache/MySQL/Perl.

      As for *why* MySQL is so much more popular than Postgres, I'm sure I don't know. I've never heard anything bad about Postgres, ever, and my own experiences with it have all been positive as well. Not that my experiences with MySQL have been bad either, granted. (The one that annoys me is MS SQL Server, which has the nasty habit of not bothering to provide extremely basic features that people who use competing products take for granted, like case-sensitive comparison and regular expression matching. Thank goodness for the third-party xp_pcre add-on, but these are NOT features one should have to install a third-party add-on in order to get.)

      > When did it change to Python and did something
      > happened to Apache while I wasn't looking?

      Nothing happened to Apache. The grandparent poster is... confused.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    32. Re:well... by jonadab · · Score: 1

      > And yeah, Perl has seen better times.

      On the contrary, Perl is more widely used now than it has ever been in the past.

      Granted, there are also some other decent options now. Fifteen years ago, for certain kinds of things, Perl was the *only* decent option, and that's no longer the case.

      But Perl is still going strong as well.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    33. Re:well... by Ecuador · · Score: 1

      When you say "more widely used", you mean as a percentage of published code? Where have you seen stats with current usage being a peak?
      Perl is actually my personal favorite language to code with, and it certainly is not dead or dying, however the decline is, unfortunately, real.
      Why do you think all the above posters forgot what the "P" really stands for? ;)

      --
      Violence is the last refuge of the incompetent. Polar Scope Align for iOS
    34. Re:well... by hardwarefreak · · Score: 3, Insightful

      Postgres is a freaking enterprise database. Its documentation is so good, it makes every other framework in my development stack look bad. But people complain because they'd rather have the easy things be trivial, without caring about the difficulty of the not so easy things.

      Some people just want their sql enabled php/java webmail app to be able to store and retrieve address book entries and what not. Should we have to become db gurus just to support such a tiny function of one of our applications? Or just to run a BBS, ahem, sorry, I mean *forum*?

      There is a finite amount of time in a lifetime. If all of us had to become an expert on every god damn piece of software we ever touch, we'd all be broke, starving, and near death. Some software, especially support software (which is what all dbs are), needs to be "drop in an go" in many cases, with little to no configuration required.

    35. Re:well... by poetmatt · · Score: 1

      BSD licenses are horrible. Really, it enables anyone to make your code proprietary at your choosing. At least with GPL if you give someone an apple they can't take away that apple and turn it into a turd.

      BSD is a "give away and pray" license.

    36. Re:well... by Skal+Tura · · Score: 2

      Amen to that!

      And that's what i tried to make my point, and being modded troll & flamebait for that.

      Added complexity adds time required to manage and get familiar, and time being a finite resource...

      That goes for code as well i have to maintain: I'll take slow & easy to maintain piece of code anyday over infinitely superior code in every other segment.
      Faster to maintain = More work done any given day, and how much i get work done is what i'm getting paid for, not the time spent on the task.

    37. Re:well... by aztracker1 · · Score: 1

      So, you're saying people, or even Microsoft shouldn't be able to give code away at their choosing?

      --
      Michael J. Ryan - tracker1.info
    38. Re:well... by Skal+Tura · · Score: 1

      That is simple sounding process, indeed. But i bet it took you more than just 3 minutes for the download alone, let alone creating a bunch of DBs, users etc.

      Your fingers can type only finitely fast, and your hand can move the mouse only finitely fast, and your internet connection finite bandwidth, and your macbook is only finitely fast.

      The reboot alone most likely took way more than the 3minutes.

      Either all of the above, or i would like to know where to get the timebubble device you are using aswell.

      Comparison CentOS, no gui installation:
      - Login as root or sudo
      - yum install mysql
      wait couple minutes for it to download and install the package
      - type /etc/init.d/mysql start
      if you want it to start automatically on reboot:
      - type chkconfig --level345 mysql on

      Done. Actual timespent is really few minutes. Ofc, add to that changing the rootpwd and creating dbs and users.

    39. Re:well... by Skal+Tura · · Score: 1

      Adding to that, there indeed is quite a bit software out there using MySQL or other databases as their backend, targeted for non-techies.

    40. Re:well... by Skal+Tura · · Score: 1

      There's nothing indicating me favoring any apple products ;) Quite the contrary. I believe apple products are crap except ease of use & marketing.

      Coding languages VS visual coding is very bad analogy, they are inherently different and targeted to different audiences. Infact, some visual coding platforms has quite a bit of success (ie. small, clone-like game development)

      Coding language VS coding language:

      PHP vs Perl
      PHP vs Ruby
      Perl VS Python
      C vs ASM
      C vs Pascal
      C vs C/C++

      A lot of these are clear: They are different level languages. ASM is way more complex than C despite having way smaller list of commands to use (ie. JMP, CMP) but they are also different level languages.

      C vs C/C++ is quite level playing field however, being on the same level.
      It's clear that C/C++ is way more powerfull than plain old C, however many argued it being too complex and sticking with C.

      There are non-techie targeted software out there using MySQL backend. I hear MythTV uses PgSql or MySql, and a program called PokerOffice aswell (tho it can use Sqlite aswell). Bottomline is, there is scenarios where non-techies as well might be use a database.

      And i weren't even talking about non-techie using a Db ... Parent was, and my point was that techies too have to put more effort in.

      And excess complicated being a bad thing, has to do with a finite resource called time, Therefore, no, i won't go in and fix PgSql, unless someone is willing to pay for it.

      and btw if you have a VPS/RPS or Dedicated, you might not be doing more complicated than necessary: Maybe you want to host a game server, or need other software not supported by your host, say a PHP module or by any other host for that matter. Most common reason is outgrowing shared hosting. There you go: A valid reason to go for more complicated system out of a necessity.

      Btw, using a dedi instead shared hosting account can make things WAY WAY simpler, especially if you manage tons of different sites.

    41. Re:well... by LS1+Brains · · Score: 1

      That is simple sounding process, indeed. But i bet it took you more than just 3 minutes for the download alone, let alone creating a bunch of DBs, users etc.

      Your fingers can type only finitely fast, and your hand can move the mouse only finitely fast, and your internet connection finite bandwidth, and your macbook is only finitely fast.

      The reboot alone most likely took way more than the 3minutes.

      Either all of the above, or i would like to know where to get the timebubble device you are using aswell.

      Comparison CentOS, no gui installation:

      Ahh, an unbeliever ;) No, my Mac reboots quite faster than three minutes. I got rid of my 1200bps modem back in 1992. I can type 140wpm. I can click with the best of 'em.

      But, who knows -- perhaps its more difficult in Linux then!! Lets test that theory, using an Ubuntu 9.10 virtual machine I happen to have on my Mac:

      brian@ubuntu:~$ time sudo apt-get install postgresql-8.4
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      The following extra packages will be installed:
      postgresql-client-8.4 postgresql-client-common postgresql-common
      Suggested packages:
      oidentd ident-server postgresql-doc-8.4
      The following NEW packages will be installed:
      postgresql-8.4 postgresql-client-8.4 postgresql-client-common postgresql-common
      0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
      Need to get 4,957kB of archives.
      After this operation, 18.2MB of additional disk space will be used.
      Do you want to continue [Y/n]?
      Get:1 http://us.archive.ubuntu.com/ karmic/main postgresql-client-common 101 [49.8kB]
      Get:2 http://us.archive.ubuntu.com/ karmic/main postgresql-client-8.4 8.4.1-1 [811kB]
      Get:3 http://us.archive.ubuntu.com/ karmic/main postgresql-common 101 [85.6kB]
      Get:4 http://us.archive.ubuntu.com/ karmic/main postgresql-8.4 8.4.1-1 [4,010kB]
      Fetched 4,957kB in 6s (764kB/s)

      Preconfiguring packages ...
      Selecting previously deselected package postgresql-client-common.
      (Reading database ... 125720 files and directories currently installed.)
      Unpacking postgresql-client-common (from .../postgresql-client-common_101_all.deb) ...
      Selecting previously deselected package postgresql-client-8.4.
      Unpacking postgresql-client-8.4 (from .../postgresql-client-8.4_8.4.1-1_i386.deb) ...
      Selecting previously deselected package postgresql-common.
      Unpacking postgresql-common (from .../postgresql-common_101_all.deb) ...
      Selecting previously deselected package postgresql-8.4.
      Unpacking postgresql-8.4 (from .../postgresql-8.4_8.4.1-1_i386.deb) ...
      Processing triggers for man-db ...
      Processing triggers for ureadahead ...
      ureadahead will be reprofiled on next reboot
      Setting up postgresql-client-common (101) ...
      Setting up postgresql-client-8.4 (8.4.1-1) ...
      update-alternatives: using /usr/share/postgresql/8.4/man/man1/psql.1.gz to provide /usr/share/man/man1/psql.1.gz (psql.1.gz) in auto mode.

      Setting up postgresql-common (101) ...
      Adding user postgres to group ssl-cert
      Building PostgreSQL dictionaries from installed myspell/hunspell packages...
      en_au
      en_gb
      en_us
      en_za

      Setting up postgresql-8.4 (8.4.1-1) ...
      Creating new cluster (configuration: /etc/postgresql/8.4/main, data: /var/lib/postgresql/8.4/main)...
      Moving configuration file /

    42. Re:well... by SanityInAnarchy · · Score: 1

      Coding languages VS visual coding is very bad analogy, they are inherently different and targeted to different audiences.

      On the contrary, they were targeted at exactly the same audience which now uses langages like PHP and Ruby -- either professionals (well, in Ruby) who value programmer productivity over raw performance, or casual users who need a shallow learning curve.

      A lot of these are clear: They are different level languages.

      I don't think so.

      PHP vs Perl
      PHP vs Ruby
      Perl VS Python

      These all attempt to fill the same niche of web development, and only PHP doesn't seem to be trying to take over as an admin/scripting language. Ruby, Perl, and Python all attempt to be general-purpose langages -- all of them have things like OpenGL bindings.

      C vs ASM

      C is exactly what I'm talking about -- when it was developed, a lot of real application and systems development was taking place in ASM. One of the things that made Unix revolutionary was that it was written in C, not ASM, which made it portable -- other OSes at the time were written in ASM for performance, but they died with the hardware they were written for.

      ASM is way more complex than C despite having way smaller list of commands to use

      In other words, ASM is way simpler than C, but more difficult to use, because C has more features. I bet it's much quicker to learn to use ASM, it's just much slower to get anything done.

      C vs C/C++

      Here, it's exactly the same thing. C++ is absolutely targeted at replacing C, and it has done so in a lot of places -- particularly as an application development language. It currently competes with C on Linux -- a lot of GNOME/GTK+ stuff is in C, and a lot of KDE/Qt stuff is in C++.

      It's clear that C/C++ is way more powerfull than plain old C

      First, I think you're confused -- "C/C++" should probably just be called C++, because C++ is a superset of C.

      But no, it's not clear. C++ is insanely more complex, with all kinds of bizarre little edge cases -- even the syntax has some perverse ambiguities. For example, templates use angle brackets for a kind of scope, but the shift operators (<< and >>) take precedence over the angle brackets used as templates. So you have things like this:

      template <class ElementOfCommutativeRingWithIdentity,
      template<typename RingElementMonomial> class TemplateMonomial>
      class TemplatePolynomial: public HashedListBasicObjects <TemplateMonomial<ElementOfCommutativeRingWithIdentity> >
      {};

      Aside from the wall of text you have to go through just to keep your types straight, look at the end of the last line. Yes, they had to put a space between those closing angle brackets, or it'd be interpreted as a >> operator.

      And the language is full of crap like that. No one can hold the entire language in their head. It's no wonder people prefer C...

      But the thing is, C has structs. C has function pointers. That's really all you need to make an object-oriented interface -- and in fact, early C++ compilers simply turned it into C and fed it to a C compiler.

      So while I've actually enjoyed getting my feet wet with C++ again lately, I'm not convinced it's better than C.

      There are non-techie targeted software out there using MySQL backend... Bottomline is, there is scenarios where non-techies as well might be use a database.

      And in those scenarios, that's really a bug in the design of that software. I will never understand why AmaroK chose to move to an embedded MySQL...

      But this is a case of using the right tool for the job. In this case, the right tool is staring you in the face: SQLite.

      But even SQLite needs maintenance, and it's up to your app to cal

      --
      Don't thank God, thank a doctor!
    43. Re:well... by poetmatt · · Score: 1

      wha? Since when has Microsoft given away actual code without a patent threat?

      GPL = you can't give it away unless you really give it away. The only restrictions are that you may not add restrictions.
      BSD = you can give it away, but with restrictions (and no definition of what those have to be).

    44. Re:well... by Anonymous Coward · · Score: 1
    45. Re:well... by aztracker1 · · Score: 1

      Read the MS-PL... anything under MS-PL says you can use this code without risk of Patent threat.... basically it's a "Don't sue us, we won't sue you" agreement. In either case, as I understand it, you are saying that people shouldn't be able to license out their code under less restrictive terms than the GPL for open-source projects?

      AFAIK, aside from Linux proper, most successful open-source projects aren't even GPL.

      --
      Michael J. Ryan - tracker1.info
    46. Re:well... by Anonymous Coward · · Score: 0

      What the fuck are you talking about? Monty isn't involved with Microsoft or their Codeplex site.

      What the fuck are YOU talking about, Holmes?

      Perhaps you missed the part where he said, "I will try to explain why I think that the CodePlex Foundation is a good idea, and why I agreed to be an advisor for the Foundation"...?

    47. Re:well... by Anonymous Coward · · Score: 0

      Ever heard of native XML support in a database system? In Postgres, that is at level 100%, in MySQL, is is about 3%. Native XML support, that is where the future of any database lies with.

    48. Re:well... by badkarmadayaccount · · Score: 1

      How much code are they gonna give away, and how much are they gonna get?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    49. Re:well... by jonadab · · Score: 1

      > When you say "more widely used", you mean
      > as a percentage of published code?

      No, I mean in terms of the total number of people using it.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    50. Re:well... by aztracker1 · · Score: 1

      Given that MS-PL is an OSI approved license, MS has released the source code for the Dynamic Language Runtime along with IronPython and IronRuby. They've also released their MVC framework as well. If you do a quick search through CodePlex, you'll find a few smaller projects as well. IronRuby as a project is hosted with Ruby proper.

      --
      Michael J. Ryan - tracker1.info
  3. so which is it? by madddddddddd · · Score: 0

    is the web going to be unrecognizable in 2020 or will monty still keep it free?

  4. How many times... by Anonymous Coward · · Score: 2, Insightful

    Will this show up every 2 weeks on /.

    1. Re:How many times... by Anonymous Coward · · Score: 0, Flamebait

      I hope that the EU hurries up and approves Oracle's acquisition of Sun, so that Oracle can finally kill MySQL. It's a product line that should've been put down well over a decade ago.

      Then we can all move on to using decent open source databases like PostgreSQL, Firebird and SQLite. We'll finally be able to use foreign keys and transactions when using the default storage engines...

    2. Re:How many times... by LizardKing · · Score: 1

      Will this show up every 2 weeks on /.

      It will probably show up regularly until Slashdot doesn't run on MySQL anymore. If they'd used a real RDBMS from the start then that clusterfuck with indexes not updating on a datatype change from a few years back wouldn't have happened.

    3. Re:How many times... by MattW · · Score: 1

      I think based on /.'s post, it would be "foreign keys not updating" rather than "indexes not updating".

    4. Re:How many times... by tolan-b · · Score: 1

      Very few people doing anything serious with MySQL use MyISAM much. InnoDB ships with it and is a nice engine.

    5. Re:How many times... by ta+bu+shi+da+yu · · Score: 1

      No, they changed the data type but the index that handles the primary key didn't update.

      Many database engines won't let you do that without dropping the index first... I think you can hardly blame MySQL for this stuff up though. And the slashdot post acknowledges this.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    6. Re:How many times... by LizardKing · · Score: 1

      Many database engines won't let you do that without dropping the index first.

      All the ones I've used will either refuse to change the data type of the column until the index has been dropped, or in the case of the better ones they will update the index. It is MySQL's fault for allowing something to happen that can screw the index. Although given my experiences with it, MySQL will often drop the index without so much as a warning or log message.

    7. Re:How many times... by LizardKing · · Score: 1

      Very few people doing anything serious with MySQL use MyISAM much.

      InnoDB doesn't support full text indexes. That means no referential integrity on any table with a full text index, so no 'Relational' in RDBMS.

    8. Re:How many times... by tolan-b · · Score: 1

      Use InnoDB (or other non-MyISAM engines) for everything and use a proper search engine for your searches...

    9. Re:How many times... by i_ate_god · · Score: 2, Insightful

      Uhm, full text indexes truly suck in the context of web application development. Perhaps you should look up Solr next time you need a search engine?

      --
      I'm god, but it's a bit of a drag really...
    10. Re:How many times... by LizardKing · · Score: 1

      Who says I'm doing web application development (not that it should matter)? And just because MySQL sucks at full text indexes doesn't mean that databases such as PostgreSQL do. Look up TSearch, which is an excellent full text indexing and search system that integrates cleanly with PostgreSQL.

    11. Re:How many times... by PCM2 · · Score: 2, Informative

      Very few people doing anything serious with MySQL use MyISAM much. InnoDB ships with it and is a nice engine.

      And (ironically?) Innobase is already a wholly-owned subsidiary of Oracle.

      --
      Breakfast served all day!
  5. Own fault by sopssa · · Score: 5, Insightful

    Maybe he shouldn't had sold it in the first time, so he wouldn't be crying it back now?

    It's like you broke up with your girlfriend and then go crying her back when she has found a new guy, while you're having no luck.

    1. Re:Own fault by Anonymous Coward · · Score: 2, Funny

      Maybe he shouldn't had sold it in the first time, so he wouldn't be crying it back now?

      Agreed. 'Crying it back' is the lowest form of groveling. Of course, I am a huge fan of Leadbelly's classic blues song "Crying It All Back Home Now."

      It's like you broke up with your girlfriend and then go crying her back when she has found a new guy, while you're having no luck.

      The concept of girlfriend?! In an explanatory analogy on Slashdot. Know your audience.

    2. Re:Own fault by Thanshin · · Score: 5, Funny

      It's like you broke up with your girlfriend and then go crying her back when she has found a new guy, while you're having no luck.

      Or, to put it in Slashdot terms:

      It's like you broke up with your car and then go crying it back when it has found a new owner, while you're having no luck finding another car.

    3. Re:Own fault by Anonymous Coward · · Score: 0

      Let me rephrase that for the audience...

      Hypothetically, it's like when your girlfriends brakes up with you, and you spam her with emails to get her back when she's found a new guy and you're not getting any.

       

    4. Re:Own fault by PizzaAnalogyGuy · · Score: 5, Funny

      If you go to a pizza joint and order a buffalo chicken style pizza with tender chicken breast, hot sauce, and onions with provolone and American cheeses on a cheddar crust, and eat it with a big glass of mountain dew, you can't just go back and say "Now that I think of it, I would rather have had Hawaiian style pan-pizza with sliced ham, bacon, pineapple and roasted red peppers with provolone cheese on a parmesan crust". You've made your deal already. If you want an another pizza, you have to buy it again.

    5. Re:Own fault by maxume · · Score: 2, Insightful

      Is it still edible if it has American cheese on it?

      --
      Nerd rage is the funniest rage.
    6. Re:Own fault by Antique+Geekmeister · · Score: 2, Interesting

      More like breaking up with his wife, signing the divorce papers and custody agreements, but now she wants to move to another state where access to his kids will be far more difficult. Because Monty went with the dual licensing model, he thought he could retain his business model as well.

      This is _exactly_ the sort of wanting to have your cake and eat it, too, model that the GPL helps _avoid_. The situation is in fact mislabeled as a GPL issue. It was the dual model, GPL for the core and BSD for business ventures model that Sun used and that Monty's later business ventures are based on, and that is now at risk.

    7. Re:Own fault by sean_nestor · · Score: 4, Informative

      FTA:

      Q: Didn't you sell MySQL to Sun? Do you want to have the cake and eat it too?

      First a little background:

      I started to work on a code that would later become MySQL in 1982. MySQL was released in 1995 under a dual licensing scheme that allowed David Axmark and me to very quickly work full time on developing MySQL.

      I lost the rights to the MySQL copyright in 2001 when MySQL AB was created and we allowed investors to come in. We needed to bring in investors to be able to create a full-scale working company to satisfy big customers and to be able to hire more developers and take MySQL to the next stage. To ensure that MySQL would continue to be free, David and I stated in the shareholder agreement that MySQL AB would have to keep MySQL under an open source license. The problem with a shareholder agreement is that it is terminated when the company is sold. This is just how things works.

      David and I however thought that this would not be a problem, as we would help ensure that MySQL would be bought by a good owner.

      I continued to lead the MySQL project and have been one of the leaders and top contributors for the project since then.

      When the sales process to Sun started, I was at the time not anymore in the MySQL Board (just a MySQL shareholder). I was just informed about the deal, after it was agreed to. I did get money for my shares, that is true, but it did not change in any way my dedication or involvement in the MySQL project.

    8. Re:Own fault by Anonymous Coward · · Score: 0
      How about technology? Its like you broke up with windows and when you couldnt play minesweeper on your new computer, you went crying back to your windows.

      Remember Slashdotters prob dont have girl friends, and they never leave their mothers bassement, so no need for a car.

    9. Re:Own fault by cc1984_ · · Score: 2, Funny

      Hypothetically, it's like when your girlfriends brakes up with you

      Goodness, the car analogies just won't stop!

    10. Re:Own fault by TheRaven64 · · Score: 2, Informative

      It was the dual model, GPL for the core and BSD for business ventures model that Sun used and that Monty's later business ventures are based on, and that is now at risk.

      Minor nitpick, but it wasn't BSD for businesses. The BSD license permits sublicensing - you can redistribute under the same terms that you received - while the MySQL commercial license does not. If it did, then there would be no problem. One of the commercial customers could simply release the code under the BSDL and everyone could use their fork.

      --
      I am TheRaven on Soylent News
    11. Re:Own fault by tushar.tyagi · · Score: 3, Insightful

      It's like you broke up with your girlfriend and then go crying her back when she has found a new guy, while you're having no luck.

      If Oracle does whatever MySQL guy thinks it'll do then that means the new guy is trying to kill your girl. In that case it's all right trying to save her.

    12. Re:Own fault by ShieldW0lf · · Score: 1

      So, the fault lies with the contributors who assigned their copyright to Monty's organization. If they had not done that, none of this drama would exist.

      --
      -1 Uncomfortable Truth
    13. Re:Own fault by MightyMartian · · Score: 1

      Well, the beauty of open source is that he can, in a way. Just fork the thing, call it MontyScrewedUpSQL or whatever and away you go. Unless, of course, he signed a non-compete, in which case it will have to be someone else.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    14. Re:Own fault by Pieroxy · · Score: 1

      Well, it is almost perfect, except that you can get back to Windows if you're not happy with your new OS. Your old gf with the big new bf is another matter altogether.

    15. Re:Own fault by Antique+Geekmeister · · Score: 1

      Oh, dear. Thank you for the correction: I should have said "BSD-like".

    16. Re:Own fault by sopssa · · Score: 4, Insightful

      David and I however thought that this would not be a problem, as we would help ensure that MySQL would be bought by a good owner.

      So it was really short-sighted thinking. They should had have some clause that limits how MySQL project would be possibly resold, or not sell the company at all, because its pretty clear that the project could be resold or go along with larger corporate overtakes. It's happened hundreds of times. They got to have known this.

    17. Re:Own fault by Pieroxy · · Score: 1

      But then it would be BSDL forever. Only the copyright owner can relicense.

    18. Re:Own fault by TheCarp · · Score: 1

      Excuse me....colorful analogies please....

      Its like he put his wife in charge of the assetts and finances so he could focus on other things, and she turned around, and sold their house.

      -Steve

      --
      "I opened my eyes, and everything went dark again"
    19. Re:Own fault by Tim+C · · Score: 2, Insightful

      Ah, but I think he wants to dual-licence it again, with a free, GPLed "community version", and a pay-for commercial version.

      He can't do that now that he no longer holds the copyright.

    20. Re:Own fault by davester666 · · Score: 1

      More like breaking up with his wife, signing the divorce papers and custody agreements, getting a large cash settlement,...

      It sounds like he wants to 'buy' back MySQL so he can go back to doing the dual-license thing [get people to do bug fixes/enhancements for free, and only he can sell the result]. Because if he just wants to make sure MySQL continues, he's free to do so as the current code base is GPL and available...

      --
      Sleep your way to a whiter smile...date a dentist!
    21. Re:Own fault by Anonymous Coward · · Score: 0

      Monty is a big hypocrite. If he is sincere with MySQL. he should not have sold it in the first place. Now if he wants it saved, let him buy back MySQL from Sun with the tons of money he raked in. I seriously doubt he would do this.

    22. Re:Own fault by smbarbour · · Score: 1

      Actually, the issue is not one of licensing. The issue is that a minor product of one company is at risk of being abandoned due to the purchase of the company by another whose major product is a competitor. That said, the GPL has it's place. It is good for making the world a better place, but it is bad for business. If one could feed a family on sunshine and rainbows, the GPL would be good in most cases.

      To put in plainly, if Microsoft released Windows under the GPL, anyone who legally acquired a copy of Windows could then take the source code, make trivial modifications, and redistribute it, and Microsoft would not see a dime from any of that. Why would anyone in their right mind use a license that undermines their business? (disregarding any argument that Windows would be made better as a result)

      Note: This post was made from a computer running Ubuntu

    23. Re:Own fault by Dragonslicer · · Score: 2, Funny

      Just fork the thing, call it MontyScrewedUpSQL or whatever and away you go.

      And it could be abbreviated MSSQL

    24. Re:Own fault by daveime · · Score: 1

      Yes, but only to people who've had their taste buds surgically removed at birth.

    25. Re:Own fault by xaxa · · Score: 1

      No... it's like you sold your car to the dealer, then leased it back from them. This was fine, the dealer kept maintaining and improving the car. But now, the dealer is being bought out by a bigger dealer. The bigger dealer only leases luxury cars, so while they'll maintain yours they'll no longer improve it, and new customers won't be able to lease the model you have.

      (I.e. MySQL will continue as an open source project, but, since it's a low-cost competitor to Oracle's main product, Oracle aren't going to improve it, and will likely make it more difficult/expensive for people to buy commercial licenses to use MySQL.)

    26. Re:Own fault by oldhack · · Score: 1

      Dang fool! You should have ordered both!

      But hold the pineapple. That's a disgrace.

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    27. Re:Own fault by Znork · · Score: 3, Insightful

      but it is bad for business.

      Bad for the selling software part of business, perhaps, but good for the buying and using software part of business. Which is the vast majority of businesses. So if you want to generalize, the GPL is without a doubt great for business.

      If one could feed a family

      Anything that helps you cut costs makes it easier to feed a family. Profitability has two parts, not only revenue but also expenses.

      Why would anyone ... use a license that undermines their business?

      Because it simply doesn't undermine most businesses. It undermines a few business models based completely on monopoly rights, but for most businesses software or software development is simply a cost centre. They get a higher profitability by cutting the costs and using (and/or modifying and/or producing) GPL software than they would by taking the whole cost themselves and having to increase revenue elsewhere.

      Microsoft would probably have a hard time switching over to the GPL+services model as they've accumulated so much fat from living in a high-margin uncompetitive segment for so long they'd get a corporate aneurysm if they actually had to shed that fat. But Microsoft is hardly the average company in the computing industry.

    28. Re:Own fault by Anonymous Coward · · Score: 0

      It's not clear to me that the American legal system really allows you to do that sort of thing; the structure of corporations is governed by some fairly specific laws, and you can't just set up whatever kind of corporate entity with whatever kind of binding agreements you want. But IANAL - one of those should weigh in.

    29. Re:Own fault by Anonymous Coward · · Score: 0

      I would say it's more like he broke up with his girlfriend, but her new boyfriend is beating her, so although he had broken up with her, he cares enough about her to try and help her out of an abusive relationship.

      I'm not suggesting the new boyfriend has a rap sheet, but the new boyfriend is already pimping his favorite girl, and the newcomer is likely to get snuffed.

    30. Re:Own fault by Anonymous Coward · · Score: 0

      except that you can get back to Windows if you're not happy with your new OS

      Not necessarily so, if it was an OEM windows install. Not without buying a new copy at least.

    31. Re:Own fault by Grishnakh · · Score: 1

      Maybe I'm missing something here, but isn't MySQL still under an open-source license? Or at least the version that was sold to Sun? Why not just fork the code, as was done with XFree86/X.org? So he might not be able to keep the same name, but who cares? Call it "NewMySQL" or "RealMySQL".

    32. Re:Own fault by EnglishTim · · Score: 2, Insightful

      Do you think they would have been able to get the investment if they had stipulated that the company couldn't be sold? I'm sure they realised that there were risks in taking the path they took; but that was the cost of being able to afford enough developers to keep MySQL competitive.

    33. Re:Own fault by Kagato · · Score: 2, Interesting

      Basically Monty fell into the classic pitfall technical people with great ideas fall into. In order to have the successful project they need money. Money in these situations typically comes from venture capital firms (investors). The stated strategy of many firms is to remove the founders (in particular when they come from a technical background) from the business side of the organization. Once a VC and their slate of investors is on the board with a significant share of the equity the downfall of the founders is assured. Sometimes they allow the technical folks to be in charge of R&D, more often than not they are shown the door (with a large chunk of money and stock in-hand).

      Products based on Open Source encourages VC firms to play nicer with company founders, but make no mistake, most VC firms want to make as much money as they can off a deal, and that usually involves selling it to a larger fish. Once a sale has occurred the stock a company founder would have is seriously diluted where at most they are a mid-tier shareholder.

    34. Re:Own fault by MightyMartian · · Score: 2, Informative

      So, in other words, he doesn't want to save MySQL, per se, he wants to have his cake and eat it too; sell MySQL for $$$ and then find a way to continue profiting from something he already sold.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    35. Re:Own fault by piquadratCH · · Score: 1

      Well, the beauty of open source is that he can, in a way. Just fork the thing, call it MontyScrewedUpSQL or whatever and away you go

      That's what he did. Admittedly, MontyScrewedUpSQL sounds a lot better than MariaDB...

    36. Re:Own fault by yttrstein · · Score: 3, Insightful

      I have to step in and say something here. If at any point in the 90s or early oughts... even up to 2004, you'd considered dropping in the ability to do hot DB dumps without table locking, you would have very likely gotten bigger than Oracle. (Much as Linux has gotten bigger than Solaris). It was idiocy of you not to do so, in favor of... god only knows what.

      And now frankly its too little, too late. MYSQL is pretty ok for a light-to-medium duty database, but you guys have had a couple of decades to really, *really* get it right, and you didn't.

      If Oracle kills MySQL, the biggest pain in the arse will be moving things over to postgresql, which everyone should have done ten years ago in the first place.

    37. Re:Own fault by Anonymous Coward · · Score: 0

      What sort of pizza joint would sell such a thing? (the buffalo chicken one)

    38. Re:Own fault by Tteddo · · Score: 1

      While I enjoy your delicious barbecue and hot sauce style pizza analogies, might I request a standard yummy tomato sauce based one next time?
      Thanks!

    39. Re:Own fault by Pieroxy · · Score: 1

      OEM Windows can be re-installed on the same machine! And you can't always buy back your former girlfriend !

    40. Re:Own fault by Anonymous Coward · · Score: 0

      Who the hell makes pizza with American cheese?

    41. Re:Own fault by montywi · · Score: 4, Interesting

      When you take in investors, it's impossible to get such a clause. (Don't think that we didn't try).

      So, in 2001, David and I had the choice to continue like before and grow slowly or take a risk and grow
      rapidly.

      Growing meant more resources for development and a better Open Source database overall. The price to pay was less control.

    42. Re:Own fault by Antique+Geekmeister · · Score: 1

      Because that license allows me, as a developer, access to the public's and my GPL peers' work to give me a base to sell my own work to people who want changes, or support. It's paying my salaries, and RedHat is profitable, so it's clearly a functional business model. And my clients pay me to help them avoid the traps of the business models you're espousing.

    43. Re:Own fault by LOLLinux · · Score: 2, Insightful

      How can Oracle "kill" MySQL? Aren't we told over and over by GNU zealots that the GPL ensures that these projects will live on forever since the source code is always available? Isn't this why they rally against the BSD-like licenses?

    44. Re:Own fault by martin-boundary · · Score: 1

      Its like he put his wife in charge of the assetts and finances so he could focus on other things, and she turned around, and sold their house.

      This is slashdot! It's like he put his car in charge of the assets and finances so he could focus on other things, and that bastard K.I.T.T. turned around and sold his house!

    45. Re:Own fault by lems1 · · Score: 1

      very well said

      --
      This sig can be distributed under the LGPL license
    46. Re:Own fault by gunith · · Score: 1

      That reply just made me hungry

    47. Re:Own fault by Anonymous Coward · · Score: 0

      My first impression was more like divorcing your wife to find out she's on her way to kill your child.

    48. Re:Own fault by blai · · Score: 1

      oooh right I get it now!

      --
      In soviet Russia, God creates you!
    49. Re:Own fault by Anonymous Coward · · Score: 0

      The beauty of Open Source is that anyone can take the source and modify it, and re-release it for free. If Oracle goes on to change the license on future MySQL versions, it won't change the fact that previous versions were open-source and can be forked into new open source projects. There is no need for a petition an appeal to keep MySQL free. Just fork it. (E.g. Joomla/Mambo).

    50. Re:Own fault by DragonWriter · · Score: 1

      When you take in investors, it's impossible to get such a clause. (Don't think that we didn't try).

      So, in 2001, David and I had the choice to continue like before and grow slowly or take a risk and grow
      rapidly.

      So, you choose a course of action, knowing the consequences that could result from it, and profited quite handsomely from it. And then, the consequences whose risk you accepted when you made the choice materialized, limiting the means by which you can derive future profit from MySQL. So, what's your beef?

  6. Me too! by TheRaven64 · · Score: 5, Insightful

    I, too, would love to sell something for a billion dollars and then have it given back.

    --
    I am TheRaven on Soylent News
    1. Re:Me too! by unwesen · · Score: 0, Redundant

      My thoughts exactly.

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

      If he wants to use the money he got from selling it to buy it back, why shouldn't he?

      It's not as if he was unaware of the danger of the death of free software.

    3. Re:Me too! by onefriedrice · · Score: 5, Insightful

      It's not as if he was unaware of the danger of the death of free software.

      The supposed death of free software and a "free internet" is just the distraction he's trying to use. MySQL is open source. Even if Oracle relicenses future releases of MySQL under terms that are less free, we still have the same MySQL as we've always had with the same free terms. If it were ever to be an issue, a fork would happen immediately and/or we'd see increased use of PostgreSQL. Either way, the "internet" will be kept free regardless. I don't know much about Monty, but my prejudgment is that he's slime.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    4. Re:Me too! by amnezick · · Score: 0

      sakila? https://launchpad.net/sakila-server
      terrible name if you ask me but who cares

      --
      mov ax,4c00h
      int 21h
    5. Re:Me too! by Pieroxy · · Score: 1

      The problem he is having (in case Oracle stops MySQL altogether) is that MySQL will be GPL forever with no more hopes for dual licensing. Well, it doesn't sound that bad from my point of view.

    6. Re:Me too! by AlexMax2742 · · Score: 1, Insightful

      ...except that if Oracle owns the copyrights to MySQL, they can close source future versions of MySQL and/or let mainline development languish. I don't know if they also own the name "MySQL" but if they do they can forbid any forks of MySQL from being called "MySQL" as well.

      Of course, the existing source will live forever, but any forks will not have the advantage of the "MySQL" brand name or the ability to dual-license the code for situations where more restrictive licensing might be desired by their customers.

      It's kind of surprising how few people realize this disadvantage of the GPL. Keep that in mind the next time you use it on a project.

      --
      I'm the guy with the unpopular opinion
    7. Re:Me too! by Anonymous Coward · · Score: 0

      > It's kind of surprising how few people realize this disadvantage of the GPL. Keep that in mind the next time you use it on a project.

      This is not a 'disadvantage' that any other licensing scheme also suffers from. You can't force developers to keep working on your favorite project.

      And it exists not because of GPL, but because of copyright law. The only way around it is to irrevocably release your code into the public domain.

    8. Re:Me too! by nomadic · · Score: 1

      ...except that if Oracle owns the copyrights to MySQL, they can close source future versions of MySQL and/or let mainline development languish. I don't know if they also own the name "MySQL" but if they do they can forbid any forks of MySQL from being called "MySQL" as well.

      A right that they paid for.

    9. Re:Me too! by Blakey+Rat · · Score: 1

      Yah. Like... this empty Coke can. Or a box of Cheerios.

      Any offers?

    10. Re:Me too! by not-my-real-name · · Score: 2, Interesting

      It's kind of surprising how few people realize this disadvantage of the GPL. Keep that in mind the next time you use it on a project.

      How is this a disadvantage of the GPL?

      If I sell software with anything like a typical commercial license and I decide to stop supporting it, you're SOL. With the GPL, at least you have the source and can spend money to hire someone to support it.

      As far as the trademark is concerned, if I own BobSQL, you can't call your own database BobSQL regardless of how either one is licensed.

      So, how is this a disadvantage of the GPL?

      --
      un-ALTERED reproduction and dissimination of this IMPORTANT information is ENCOURAGED
    11. Re:Me too! by tolan-b · · Score: 1

      How would another license fix either of these potential problems exactly?

    12. Re:Me too! by al3 · · Score: 1

      If I had a billion dollars I'd try to think of ways to make the world better too. Undoing what got you the $1B is a little strange, but whatev.

    13. Re:Me too! by ClosedSource · · Score: 1

      It's not true that this is a GPL-specific problem. On the other hand, it does blow a big hole through the argument that the GPL is better than BSD because the former "keeps the code free" and the latter doesn't.

    14. Re:Me too! by narrowhouse · · Score: 1

      Just curious, when you say "situations where more restrictive licensing might be desired by their customers", can you tell me why a customer would prefer a MORE restrictive license? I can understand why someone may want to sell under a dual license by why would a customer want more restrictions on what they can do with the code? I just don't hear "Yeah, this is great, could you just put a few more restictions on what I can do with the source code?" a lot.

      --


      Insert pithy comment here.
    15. Re:Me too! by _Sprocket_ · · Score: 2, Insightful

      ...except that if Oracle owns the copyrights to MySQL, they can close source future versions of MySQL and/or let mainline development languish. I don't know if they also own the name "MySQL" but if they do they can forbid any forks of MySQL from being called "MySQL" as well.

      Of course, the existing source will live forever, but any forks will not have the advantage of the "MySQL" brand name or the ability to dual-license the code for situations where more restrictive licensing might be desired by their customers.

      It's kind of surprising how few people realize this disadvantage of the GPL. Keep that in mind the next time you use it on a project.

      So I'm curious - what license does a better job at this than the GPL? What license specifically provides access to a trademark and negates dual-licensing? Or was dual-licensing the advantage? You know - the advantage of shutting down future forks. Just like Oracle is feared to do. Which is an issue. Except when everyone else wants to do it. Then that's an advantage. Right?

    16. Re:Me too! by montywi · · Score: 2, Informative

      Yes, you can use the old version of MySQL, but there is no guarantee that a fork will come up and be able to continue development if Oracle slowly starts to close up MySQL development.

      The reason is that if MySQL is only available under GPL, there will be very few companies that can make direct revenue on MySQL and because of this, there is very little incentive to put money into MySQL development.

      All GPL libraries have the same problem, which is the reason why there is so few GPL libraries that are actively developed.

      Look at PostgreSQL for example; Many core developers works at a companies that is using PostgreSQL with proprietary code. If PostgreSQL was under GPL, they could not do that and would not have an incentive to do development on it.

    17. Re:Me too! by eliot1785 · · Score: 1

      Everybody is focusing on copyright law, but I don't think that is the only issue. Most countries also have laws against anti-competitive behavior (i.e. anti-monopoly laws), which govern corporate acquisitions, among other things. While an Oracle-MySQL combination would still have competitors (PostgreSQL, MSSQL, etc), it would also have an enormous amount of market power in the database world. For this reason, it's not surprising to see the deal raise flags, regardless of the final outcome of the proceedings.

      Coke would not be allowed to acquire Pepsi for similar reasons. This is not a Coke-Pepsi situation, but it's also not like one corner store acquiring another corner store. The reason that this approval process exists in the first place is that we know that these concerns are often legitimate.

    18. Re:Me too! by AlexMax2742 · · Score: 2, Interesting

      If I sell software with anything like a typical commercial license and I decide to stop supporting it, you're SOL. With the GPL, at least you have the source and can spend money to hire someone to support it.

      The GPL emphasizes code freedom over developer freedom. Take a look at Question 6 of the Commercial License page for MySQL:

      Q6: What is Sun's commercial license for MySQL software?
      A: Sun offers a commercial license for all of its MySQL software that is embedded in or bundled with another application. The commercial license allows OEMs, ISVs and VARs to distribute commercial binaries of MySQL software with their own commercial software without subjecting that software to the GPL and its requirement to distribute source code.

      Emphasis mine. If MySQL had been BSD licensed, Monty Program AB could continue to offer a similar service for MariaDB, even though it was not the primary copyright holder of MySQL's codebase. Of course, said commercial software would have to have the BSD license included somewhere in their documentation, per the BSD license's second clause, but this is likely to be far more agreeable than the GPL's onerous requirements.

      As far as the trademark is concerned, if I own BobSQL, you can't call your own database BobSQL regardless of how either one is licensed.

      You are precisely correct. However, I feel that too many GPL advocates don't think about the ramifications of having to discard the brand associated with the code. "Oh we'll fork it and everything will be fine" is naive, since you now have to "get the word out" about the forked project all over again. And this is only if the copyright holders have abandoned the project, if they continue to develop it, you are now effectively competing against your old established codebase and have more to prove.

      Looking back over my original post, however, it does look like I put the branding issues and the 'commercial closed source' issue under the same umbrella, though I meant differently (see: singular use of the word "disadvantage") My apologies.

      --
      I'm the guy with the unpopular opinion
    19. Re:Me too! by toby · · Score: 1

      there is very little incentive to put money into MySQL development.

      Unless you own it.

      If PostgreSQL was under GPL, they could not do that and would not have an incentive to do development on it

      So why did you use EnterpriseDB as a counter-example in your blog? BSD prevents bidirectional community involvement. It makes taking easy but when you give back, you do not give back to a community.

      You wrote: The PostgreSQL market is also, as far as I know, dominated by Enterprise DB that provides a closed source version of PostgreSQL, which is not good enough for companies standardizing on open source.

      Q.E.D.

      --
      you had me at #!
  7. Go on, by Anonymous Coward · · Score: 0

    take the money and run...

  8. Not just his blog by dals_rule · · Score: 5, Informative

    He also spammed everybody who's ever been dumb enough to let him get anywhere near their e-mail address with the same self-serving, hypocritical screed...

    1. Re:Not just his blog by Anonymous Coward · · Score: 0

      That sounds like the rant of one of the dumb enough.

    2. Re:Not just his blog by Anonymous Coward · · Score: 2, Informative

      I can confirm this. I have merely helped post some bugs from Debian to MySQL dev's bug tracker and now I was spammed by "save my MySQL project".

      The entire request is dumb and goes against the merits of what MySQL AB did under his apparent leadership. Remember when they have changed LGPL libmysqlclient library to GPL only and told commercial or other non-free devs to pay up? Now, he wants EU to force Sun/Oracle to release MySQL again under BSD or something? WTF? Now that's hypocrisy!

      Monty, you *SOLD* MySQL AB. That means you *chose* to move on from controlling the project, or have any future say on how it works. Period. Now, walk away. It is not your project anymore.

      PS. I've moved to PostgreSQL after MySQL changed licenses in 4.0.x time and I couldn't be happier. Finally, a database that works and is free.

  9. No he doesn't by wiredlogic · · Score: 5, Informative

    This has been hashed out before. Monty wants to force the legitimate owner of MySQL to give up its rights to the documentation and proprietary parts of the source code so he can deploy his own commercial product using MariaDB. It's that simple. He got a big payoff when he cashed out and now he wants to double dip by getting back for free what he has already been compensated for.

    --
    I am becoming gerund, destroyer of verbs.
    1. Re:No he doesn't by dkf · · Score: 1

      He got a big payoff when he cashed out and now he wants to double dip by getting back for free what he has already been compensated for.

      He could offer to purchase the proprietary parts off Sun using some of that money he got paid for selling out in the first place. Otherwise, well, it's now Sun's (and so Oracle's if Larry Ellison can stop himself from insulting the European Commission even further) and Monty will just have to console himself with looking whiny and sniveling. Or he could try hookers and blackjack.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    2. Re:No he doesn't by JSBiff · · Score: 4, Interesting

      There's an interesting thing hidden in this whole mess. . . The argument that Monty makes for why he doesn't think MySQL can survive as a strictly GPL product is that it would cut off the ability of him and others to make money selling non-GPL products which *link* to MySQL. This is based upon the notion that dynamically linking an executable with a GPL library (or linking a non-GPL library with a GPL executable) violates the GPL - which of course is an assertion the FSF likes to make. I am not a lawyer, but I've tried to research this and find an answer to the following question: does dynamic linking actually create a copyright infringement situation (i.e. a derivative work)?

      From a technical standpoint, you can argue back and forth on the merits all day. But, from a standpoint of the law, so far as I've been able to tell, this is a question that has never been addressed by courts or legislation. Personally, I feel the most reasonable interpretation (from the standpoint of being consistent and, well, logical) would be that linking does *not* create a derivative work (for example, is Firefox a derivative of the Flash plugin, or Flash plugin a derivative of Firefox? Seems to me they are fairly independent works that use the mechanism of dynamic linking to work together.)

      But, I also agree with other posters that Monty got a Billion bucks, and now wants to get MySQL back, and that's just kind of shady. You sell something, you get paid, it's not yours anymore. Maybe Monty can *buy it back* from Sun before they sell to Oracle - seems like that would be fair to all parties involved, and clear the way for the Oracle/Sun merger.

    3. Re:No he doesn't by jrumney · · Score: 2, Insightful

      The Flash plugin does not merely use dynamic linking to create a derivative work of Firefox. It uses a published API for the express purpose of making such plugins, with permission granted by the original author of that API - Mosaic Communications Company.

    4. Re:No he doesn't by fatp · · Score: 2, Informative

      The problem is not linking a library binary object. Instead, it's the use of header files during development.

    5. Re:No he doesn't by JSBiff · · Score: 1

      ". . .it's the use of header files during development."

      And this gets into those arguments which I said could last all day - because it's not really clear whether using a header file during development actually creates a derivative work. I don't have the URL handy right now, but I seem to recall during the SCO Saga that SCO made a claim about a header file violation by the Linux Kernel and ELF libraries, and it seems like the resolution of that claim was something to the effect that header files (in particular, symbolic constant names, values, and function/class/variable names) are not protected by copyright because they are necessary for interoperability or something along those lines. Again, I am not a lawyer, but I just remember reading that and thinking that kind of blows a hole in the claim that a dynamic library violates copyrights (in general) of the work it is linked against.

      But, there might be counterarguments that can be made. So, I go back to my original point, technical merits notwithstanding, so far as I know, this is not a settled matter of law, and so it is at least *possible* that you could actually legally link a commercial library or client app against MySQL without violating the GPL (the claims the GPL itself makes notwithstanding). But, since it's not settled, the first person/company to try this is making a real legal crap-shoot, and better hope they have the right lawyer to make the argument to the courts for why this *should* be legal.

    6. Re:No he doesn't by Pieroxy · · Score: 1

      Maybe Monty can *buy it back* from Sun before they sell to Oracle - seems like that would be fair to all parties involved, and clear the way for the Oracle/Sun merger.

      Well, maybe not for Oracle, unless you don't count them as a party involved. Maybe, just maybe, they are interested by MySQL, would it be to kill it.

    7. Re:No he doesn't by shutdown+-p+now · · Score: 2, Interesting

      The problem is not linking a library binary object. Instead, it's the use of header files during development.

      If that is the case, the trivial workaround would be to write all function prototypes and type declarations yourself (e.g. from the docs, or via clean-room reverse engineering).

      Furthermore, Java doesn't have headers. And FSF insists that "dynamically linking" (of course, it is always dynamic in Java) against a GPL'd Java class library results in a derived work as well.

    8. Re:No he doesn't by Anonymous Coward · · Score: 0

      dynamic linking is linking, period.

      firefox exports API that Adobe uses for flash integration, period. Even Adobe calls flash a plugin, but you somehow missed those press releases?

      You see, exported API comes with a license. As soon as you use that API, you are linking. Be it Win32, or libc or whatever. There is a license attached to these API calls. There is a reason why Linux is GPL, but exports userland API under an exception.

      The solution is simple, do not use API you can't use as per licensed terms.

      Your argument is like saying oral sex is not sex. :P

    9. Re:No he doesn't by JSBiff · · Score: 3, Insightful

      You still haven't explained how a derivative work is created. You make an appeal to authority where you have none, period. (See, wasn't that easy?)

      Copyright law governs the distribution of copies of a protected work. That's all. It doesn't govern use (although, sometimes, contracts are used as part of the licensing agreement to receive a copy for proprietary software, which can add further restrictions). But the GPL is not a contract, it is a license, and only covers the work it was applied to, and any *derivative works*.

      The thing is, even though the linked library or EXE uses the API, it doesn't *contain* the API. So, the argument can be made that where there is no copying, there is no copyright violation. Put another way, there is a very logical argument that a dynamically linked work is completely separate from the executable or library it links against. Think of a book or magazine article, or even an article on a website, which directs the reader to go read something else, then come back and finish reading the text of the article. Is the article a derivative work of the work it references/links to?

        Hence, even though the library or exe *depends* upon the other work, it may not be a derivative because it does not *contain* the other work (or, perhaps the courts will decide that it *is* in fact, a derivative, but no one really knows for sure). See, like I said, we can argue about this all day, but the question is still not settled in law. The law, so far as I know, *does not* address the question of dynamically linking computer programs in any statute or court precedent.

      "Your argument is like saying oral sex is not sex."

      No, it's not. It's nice you're so opinionated, but that makes no sense.

    10. Re:No he doesn't by MartinSchou · · Score: 2, Insightful

      "Your argument is like saying oral sex is not sex."

      No, it's not. It's nice you're so opinionated, but that makes no sense.

      It's more like saying "Oral sex can't get you pregnant".

    11. Re:No he doesn't by Anonymous Coward · · Score: 0

      You are a moron. There is no difference between static and dynamic linking on non-Windows OSes (Windows does extra stuff, but basically it is also linking). If you knew how a linker works, you would know this.

      If you do this to any of my software, I'll see you in court. Too bad for you, your argument has been tested with non-GPL software a few times already and failed miserably. Just because it is GPL does not imply copyright law is somewhat different.

      ""Your argument is like saying oral sex is not sex."
      No, it's not. It's nice you're so opinionated, but that makes no sense."

      FFS, you are a moron. What's next stupid comment from you? Don't tell me, I don't want to know.

    12. Re:No he doesn't by montywi · · Score: 2

      I haven't asked Sun to give up anything

      I have however pointed out the reasons why one can't assume that a fork will suddenly spring up and be able to resurrect MySQL if Oracle would decide to kill it (as others seam to think). The manual is one reason, the GPL license is another.

      And MariaDB is not commercial; It's only available under Open Source.

      What we are asking for in the petition is that MySQL users should be heard in the process.
      By asking MySQL to be divested to another entity, there is no money for me to make (actually less, as you should know if you have read my blog)

    13. Re:No he doesn't by montywi · · Score: 2, Interesting

      To make it clear, I don't want MySQL back.

      I just want that MySQL should be owned by someone that have more reasons to keep it alive than to kill it.
      (which is not me). This to ensure that the project is kept alive as an Open Source project also in the future.

    14. Re:No he doesn't by montywi · · Score: 1

      Note that GPL is based on distribution, not linking.

      If you distribute your shared closed source library with the GPL code that uses the library, the whole is a derivated work of the GPL code and the shared library is thus affected by the GPL.

    15. Re:No he doesn't by kermyt · · Score: 1

      not that I necessarily agree with this concept, but the idea is that a copy is made when an API call pulls a function off of the storage medium (hard drive for instance) and places the working copy of it linked into memory. That _is_ a copy, however volatile it might be.

    16. Re:No he doesn't by maestroX · · Score: 1

      Note that GPL is based on distribution, not linking.

      JSBiff points out that dynamic linking crosses the border between license and copyright due to the concept of 'derivative works'. Derivative works is a key ingredient of copyright. You, whoever may want or claim 'derivative work' is also part of the GPL license.
      If so, the GPL is not merely based on distribution, but also on copyright. Point is, the 'derivative work' concept isn't tried in court to supply a sufficient legal definition and set the boundaries.

    17. Re:No he doesn't by LOLLinux · · Score: 1

      Maybe, just maybe, they are interested by MySQL, would it be to kill it.

      1) You can't kill GPL code.
      2) If he was this worried about it he shouldn't have sold MySQL in the first place.

      He's just butthurt because he can't make a closed-source fork of MySQL. Sorry, if I don't feel any sympathy at all for him and his billion dollars.

    18. Re:No he doesn't by FilthCatcher · · Score: 1

      Furthermore, Java doesn't have headers. And FSF insists that "dynamically linking" (of course, it is always dynamic in Java) against a GPL'd Java class library results in a derived work as well.

      Which is why a number of Java library projects that don't object to the jars being used by commercial software release under a "GPL with classpath exception" license. I always imagine this license sitting somwhere between GPL and LGPL.

    19. Re:No he doesn't by LurkerXXX · · Score: 1

      Of course it's shady what else did you expect?

      Anyone familiar with MySQL knows 'integrity' is not on the top of Monty's list of priorities.

      Data integrity, personal integrity, bah.

    20. Re:No he doesn't by toby · · Score: 2

      MariaDB is not commercial; It's only available under Open Source

      And you claim above, and on your blog in several contexts, that under GPL there is "no incentive to invest in development" and "direct revenue" cannot be generated, MariaDB itself lacks a viable business model and will eventually run out of funds. The only rational step is to cancel that project, unless you believe something is about to magically change, and a BSD-like license (anything but that pesky GPL!) were suddenly to allow MariaDB to demand "direct revenue" from its development fruits.

      You seem to believe this is the only way the community should go forward, as a whole - if we overlook the contradictory aside on EnterpriseDB.

      You claim MPAB would produce "only BSD" code in MariaDB, but we have only your word for this. And you have omitted to mention how MariaDB development is funded under this model. You claim the only money to be made in the community is by eliminating the GPL, yet your own company will altruistically refuse to take advantage of such a license to sell closed enhancements, while it burns up your cash? This is stretching credibility.

      (If I wanted to be terribly cynical, I'd point out the loophole that *another* Monty Company could take on commercial extension of BSD code without breaking the letter of your promise, while being lucrative to you, and perhaps even keeping MariaDB alive financially - latter to the community's benefit, naturally - but this isn't spelled out on your blog. This model is not so dissimilar from that allowed to a copyright holder under GPL, of course. But by keeping development partially closed you begin to encroach on those sins you expect from Oracle.)

      It seems as if you are conflating a personal preference for this business model with the entirely separate possibility of a healthy community continuing around the GPL code. The point is not that your critics have better facts about outcomes if the sale proceeds, or if MySQL were not GPL, but that your own statements are so self-contradictory. Furthermore they are easily misconstrued in unflattering ways, as so many commenters here have done. Personally I am not accusing you of greed, but prefer to infer a forgivable irrationality.

      --
      you had me at #!
    21. Re:No he doesn't by shutdown+-p+now · · Score: 1

      Which is why a number of Java library projects that don't object to the jars being used by commercial software release under a "GPL with classpath exception" license.

      But that's not GPL - it's why the exception is there in the first place! So, presumably, without the exception you cannot link to GPL'd Java code.

      I do suspect it would be a tough sell in court, though, given that Java linking is on class API level - meaning that one can just replace any given .class file with his own with the same public/protected members and have it "just work"; and no source code nor bytecode of the class linked against is present in the compiled linking binary.

  10. Stick a fork in it! by Anonymous Coward · · Score: 0

    Why doesn't he just fork the whole project? He is the original author so many contributors would likely follow him. That would be a much easier way to maintain some control IMHO.

    1. Re:Stick a fork in it! by tepples · · Score: 2, Interesting

      Why doesn't he just fork the whole project?

      The article addresses the forking issue.

    2. Re:Stick a fork in it! by Anonymous Coward · · Score: 3, Informative

      Why doesn't he just fork the whole project?

      He has, it's called something like mariadb. Two problems: No one has ever heard of his fork, and what he really wants is the proprietary parts that were developed when mysql (the corp) was under his control.

    3. Re:Stick a fork in it! by dkf · · Score: 1

      The article addresses the forking issue.

      What it doesn't address is the fact that if he'd really wanted to truly keep the commercial people onboard while a change of ownership is going on, the GPL was not the best license to use in the first place. But too late for that now; the MySQL community is screwed unless Oracle turn out to be a nicer owner than expected (or it gets blocked by the Commission, but I doubt Monty's pathetic whining will help there).

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    4. Re:Stick a fork in it! by jvillain · · Score: 3, Insightful

      There is a third problem. No one is going to risk their business on Monty's fork or sign over their patches because the risk is so great that he will sell every one out again. The fact that he is fully in bed with Microsoft on this makes it even more likely. Fool us once shame on you, fool us twice shame on us.

    5. Re:Stick a fork in it! by TheRaven64 · · Score: 1

      No, the MySQL community will be fine. The MySQL community can fork the GPL'd version. The MySQL commercial customers are the only ones that will suffer.

      --
      I am TheRaven on Soylent News
    6. Re:Stick a fork in it! by vlm · · Score: 1

      Why doesn't he just fork the whole project?

      The article addresses the forking issue.

      I read the whole long forking article. Am I paraphrasing and summarizing it correctly: a GPL mysql would never survive without the technical contributions from the dual licensed customers, because the dual licensed customers payed money to buy a commercial license that does not be require them to make technical contributions? It read like a bunch of nonsense without logical arguments but including lots of FUD.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    7. Re:Stick a fork in it! by zotz · · Score: 1

      Basically,

      unless you *must* have a non-Free play, you can fork it.

      So, he is not likely to get any love from those who think non-Free is wrong.

      To me, his belief that he *must* have a non-Free play is what is keeping him from forking it.

      Just fork it and play totally Free already.

      Now, I would be happy to learn of mistakes with the above thinking. Educate away.

      all the best,

      drew
      Check out the Free Music Push

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    8. Re:Stick a fork in it! by zotz · · Score: 1

      "As only the original rights holder can sell commercial licenses, no new forked version of the code will have the ability to practice the parallel licensing approach, and will not easily generate the resources to support continued development of the MySQL platform."

      But...

      Once you go the all Free route, don't assign your copyrights to Oracle or the original MySQL branch.

      Now, no one will be able to sell non-GPL licenses to this code base. Not the people heading this fork nor the people owning the original, dual-licensable, code.

      So, if the fork does a better job of improving things than the original code owners, that is the code people will want.

      In order to keep selling the code with non-GPL licenses, the owners will have to bear the whose cost of keeping the code improved. And try to succeed in selling inferior code at high prices. Good luck with that.

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    9. Re:Stick a fork in it! by thePowerOfGrayskull · · Score: 2, Insightful
      Except it doesn't, really. To paraphrase: "The OSS community can't succeed at managing a project without a driving corporate interest". I think there are many, many thriving examples that prove that statement to be blatantly false.

      If you look a little closer at his words, you'll see that he's really saying MySQL can't succeed commercially as open source. This is, of course, true: a product that isn't commercially maintained can't be a commercial success. Fortunately, it doesn't need to be a commercial success in order to succeed.

    10. Re:Stick a fork in it! by phantomfive · · Score: 1
      In case anyone is wondering, this seems to be the most important point in my mind:

      There's always talk about a "fork", meaning an independent, derived version of MySQL. The GPL would allow that to happen but would not allow it to work out successfully. Not only would the "fork" start without the famous MySQL name but also would the "fork" not be usable by everything, for example with closed source applications, plugin or storage engines which are part of the current MySQL ecosystem

      This is what happens if you don't make your project completely open source from the beginning.

      --
      Qxe4
    11. Re:Stick a fork in it! by rbanffy · · Score: 1

      The MySQL proprietary customers are the only ones who will suffer.

      There. Fixed for you.

      There are lots of commercial customers of the GPL version that won't notice the change.

    12. Re:Stick a fork in it! by rbanffy · · Score: 2, Interesting

      It basically goes like this "we got paid by the folks who wanted MySQL for proprietary software to make enhancements that we could, if we wanted, include in the GPL versions".

      This asymmetry - when a customer pays MySQL for a proprietary license, MySQL gets developer attention it would not get otherwise - may have distorted the free database market giving MySQL more resources than it rightfully deserved.

      But that's a good subject for a thesis I am not willing to defend.

    13. Re:Stick a fork in it! by rbanffy · · Score: 1

      Drizzle! Drizzle!

  11. Not a valid argument... by filesiteguy · · Score: 1

    I read the blog/petition last week. (What else is there to do at work between Christmas and New Year's?)

    I understand the concern - that MySQL will be an in-house "competitor" for resources to Oracle's database. However, why wouldn't they be complimentary?

    Also, since a large portion of the original MySQL is OSS, then I see no reason an entity couldn't take it and create a forked product to compete in that space. This would be like Websphere and Apache co-existing. IBM goes after the corporate market and Apache goes after the rest.

    1. Re:Not a valid argument... by tepples · · Score: 1

      Also, since a large portion of the original MySQL is OSS, then I see no reason an entity couldn't take it and create a forked product to compete in that space.

      An Anonymous Coward asked the same question; please see its answer.

    2. Re:Not a valid argument... by itsdapead · · Score: 1

      I see no reason an entity couldn't take it and create a forked product to compete in that space

      No, but there is a built in inequity: anybody developing a fork from the GPL code base is obliged to release their products under the GPL. Even if they're happy to contribute their own work to the community, that makes it harder to develop products that are interoperable with other proprietary systems and/or which might have patent issues.

      Oracle, on the other hand, will own the copyrights and therefore are not bound at all by the GPL. They would be free to distribute MySQL-based products or MySQL clients with, for example, better integration with Oracle, Windows, .NET or IIS. They could even bolt on a proprietary DB engine...

      Now, if you are a GPL purist this won't worry you, since you'd rather shave your own head with a cheesegrater than use proprietary code (and you're probably using PostgreSQL anyway), but if you're more pragmatic and interested in commercializing MySQL-based products then it means Oracle have a potential competetive edge.

      Of course, in the past you could always approach Monty or, later, Sun and ask for a license to distribute MySQL or its libraries outside the GPL. Now you'll have to ask Oracle - and its their position as a dominant player in the database industry that is the real cause for concern. That's also the anti-competition justification that may give the EU the right to intervene.

      However, why wouldn't they be complimentary?

      Depends whether you see MySQL in its traditional role as a "lite" DBMS which perfectly nails the sweet spot as a backend for blogs and web shops, or as a potential Oracle/MSSQL-killer dealing reliably with complex transactions and squillions of tables. I'm sure its creators see it as the latter, but I've always felt that adding transactions and referential integrity was a bit like putting airbags on a pushbike...

      --
      In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
    3. Re:Not a valid argument... by Blakey+Rat · · Score: 1

      I understand the concern - that MySQL will be an in-house "competitor" for resources to Oracle's database. However, why wouldn't they be complimentary?

      That's the big mystery.

      Microsoft seems to be doing ok with both SQL Server and SQL Server Express. It helps that the migration between the two is mind-numbingly simple.

      If Oracle set up an easy way to migrate from MySQL to Oracle, and they renamed MySQL into "Oracle Express", there you go.

    4. Re:Not a valid argument... by filesiteguy · · Score: 1

      Brilliant point!

      I use both SQL Server (on my enterprise-level servers), SQL Express (on my laptop under VMWare) and also am a user of MySQL on my personal website as well as a few other websites.

      I see no reason for it to be a zero-sum game. Oracle would actually benefit by having an entry-level database as well as an enterprise-level one.

    5. Re:Not a valid argument... by Sxooter · · Score: 1

      Now, if you are a GPL purist this won't worry you, since you'd rather shave your own head with a cheesegrater than use proprietary code (and you're probably using PostgreSQL anyway)

      If you are a GPL purist, you are almost certainly not running the BSD-licensed PostgreSQL...

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    6. Re:Not a valid argument... by VGPowerlord · · Score: 1

      I understand the concern - that MySQL will be an in-house "competitor" for resources to Oracle's database. However, why wouldn't they be complimentary?

      That's the big mystery.

      Microsoft seems to be doing ok with both SQL Server and SQL Server Express. It helps that the migration between the two is mind-numbingly simple.

      If Oracle set up an easy way to migrate from MySQL to Oracle, and they renamed MySQL into "Oracle Express", there you go.

      Rather than, say, Oracle Database Express Edition (XE)?

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    7. Re:Not a valid argument... by ge · · Score: 2, Insightful

      If you're a GPL fundamentalist you get what you deserve: you get to run a GPL MySQL version.

  12. Econ 101: if a niche needs filled, it will be by SlappyBastard · · Score: 1

    How intellectually lazy is it to say there won't be a free DB? Do I want to migrate from MySQL to PG? No. But, if the economics of MySQL become prohibitive, it's not like I'm going to kill myself over it. I'm going to move on.

    If the existing solutions aren't good enough, then a new solution will emerge. That's economics. The niche is already proven by MySQL. If MySQL ceases to fill that niche, it won't be long before something else fills it.

    --
    I scream. You scream. I assume that means we're both acquainted with the problem. We proceed.
    1. Re:Econ 101: if a niche needs filled, it will be by TheRaven64 · · Score: 1

      Actually, as far as I can tell, he's not saying there won't be a free DB. He's saying that you can fork the code but not the ecosystem, which is nonsense. Look at X.org for a counterexample; if the original is not being invested in (which he claims he fears) then the fork becomes the official version. The only one of his complaints that makes sense is that Oracle might discontinue commercial licenses for MySQL. The only reason that you need a commercial license for MySQL is if you are going to distribute a product that incorporates a product and is not GPL'd. Quite why you'd pick MySQL if you wanted a database to incorporate into your product instead of SQLite or PostgreSQL, I have no idea.

      --
      I am TheRaven on Soylent News
    2. Re:Econ 101: if a niche needs filled, it will be by SlappyBastard · · Score: 1

      His "Help keep the Internet free" stuff implies that without MySQL there's nothing.

      --
      I scream. You scream. I assume that means we're both acquainted with the problem. We proceed.
    3. Re:Econ 101: if a niche needs filled, it will be by tepples · · Score: 2, Informative

      Quite why you'd pick MySQL if you wanted a database to incorporate into your product instead of SQLite or PostgreSQL, I have no idea.

      Shared web hosting providers offer only MySQL, not PostgreSQL. If you want PostgreSQL, that's a lot of money to move up to a virtual dedicated server.

      SQLite isn't intended for high levels of concurrency; its locking is much coarser. One gets plenty of "OperationalError: database is locked". And it only recently gained support for foreign key constraints and data type constraints (by compiling them into triggers) in a newer version that hasn't yet made it into long-term-supported server operating systems such as CentOS 5.x and Ubuntu 8.04.

    4. Re:Econ 101: if a niche needs filled, it will be by TheRaven64 · · Score: 2, Informative

      Shared web hosting providers offer only MySQL, not PostgreSQL. If you want PostgreSQL, that's a lot of money to move up to a virtual dedicated server.

      Not entirely true, lots of shared web hosts also provide PostgreSQL, but completely irrelevant. I have never seen a shared web host that runs software that bundles MySQL. They may have third party software that uses MySQL via PHP, for example, but this does not need a commercial license.

      SQLite isn't intended for high levels of concurrency; its locking is much coarser. One gets plenty of "OperationalError: database is locked". And it only recently gained support for foreign key constraints and data type constraints (by compiling them into triggers) in a newer version that hasn't yet made it into long-term-supported server operating systems such as CentOS 5.x and Ubuntu 8.04.

      Again, you're talking about having SQLite installed already, not bundling it with your commercial code. If you need a small db, you can link SQLite directly into your app. If you need a bigger db, you can require the user has Oracle or PostgreSQL installed. You don't to ship a db with your app. If you want to interface with MySQL, then you use one of the permissively-licensed MySQL client libraries. You only need a commercial license for MySQL if you are going to be shipping a copy of MySQL along with your code.

      As for foreign key constraints, you realise that these are still pretty new in MySQL, right? Until around 2002 or so, MySQL users and developers were claiming that no one needed them...

      --
      I am TheRaven on Soylent News
    5. Re:Econ 101: if a niche needs filled, it will be by metamatic · · Score: 2, Informative

      Shared web hosting providers offer only MySQL, not PostgreSQL.

      Maybe the really crap ones. I have shared hosting with PostgreSQL for a few bucks a month. I mean, Cpanel has full PostgreSQL support, it's not like the hosting provider has to do a lot of work.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    6. Re:Econ 101: if a niche needs filled, it will be by tepples · · Score: 2, Informative

      They may have third party software that uses MySQL via PHP

      PHP is under a GPL-incompatible license. If Oracle terminates the FOSS exception for new versions of the MySQL client library, hosts won't be able to use PHP with new versions of the MySQL client library.

      you use one of the permissively-licensed MySQL client libraries.

      I've read posturing from MySQL AB or Sun (I don't remember which) that the permissive licenses on these client libraries are invalid because either A. the very act of using MySQL's wire protocol is considered "combining modules into one Program", B. MySQL uses patented methods licensed only for use with programs that use the GPL client library, or C. both. It might be FUD, but FUD can be effective in today's lawsuit-happy business environment.

    7. Re:Econ 101: if a niche needs filled, it will be by tepples · · Score: 1

      As for foreign key constraints, you realise that these are still pretty new in MySQL, right?

      In MySQL, foreign key constraints are old enough that enough hosts have already upgraded to a version that includes them. In SQLite, they are not old enough in my experience.

    8. Re:Econ 101: if a niche needs filled, it will be by rbanffy · · Score: 1

      He will still have his billion dollars.

      Seriously, he should STFU and enjoy his retirement. I most certainly would.

    9. Re:Econ 101: if a niche needs filled, it will be by Anonymous Coward · · Score: 0

      They may have third party software that uses MySQL via PHP

      PHP is under a GPL-incompatible license. If Oracle terminates the FOSS exception for new versions of the MySQL client library, hosts won't be able to use PHP with new versions of the MySQL client library.

      This is only partly true -- since MySQL is dual licensed, if Oracle terminates the FOSS exception for new versions, it gets forked and the forked version will continue to be used for PHP stacks. Since this is one of the main uses for MySQL, the GPL version will mirror the changes or risk being marginalized.

      In summary, if Oracle doesn't continue to maintain things in a way that supports the PHP crowd, they will lose control of MySQL.

    10. Re:Econ 101: if a niche needs filled, it will be by Anonymous Coward · · Score: 0

      If Oracle terminates the FOSS exception for new versions of the MySQL client library, hosts won't be able to use PHP with new versions of the MySQL client library.

      With any luck, that'll kill both MySQL and PHP.

  13. Ob by Hognoxious · · Score: 1

    Vot about Rommel?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    1. Re:Ob by Anonymous Coward · · Score: 1, Insightful

      You know, sadly, nobody is going to get that, right?

    2. Re:Ob by sjaskow · · Score: 1

      I got it but I'm a geek for WWII trivia. And comparing Rommel to Monty is like comparing Bill to Darl. :)

    3. Re:Ob by Anonymous Coward · · Score: 0

      I'm not so sure about that. Rommel was a competent general and was smart enough to try to kill Hitler before it was too late for Germany. At some point, Bill and Monty both wrote code which was useful to people. Has Darl ever done anything useful or has he always been a parasite?

  14. He got paid. It's GPL. by bcrowell · · Score: 3, Insightful

    He got paid a large amount of money for MySQL, and now he's not satisfied. MySQL is under GPL v. 2, so there isn't a problem. If Sun takes it in a bad direction, it can be forked.

    1. Re:He got paid. It's GPL. by stakovahflow · · Score: 1

      Ah, fork it...
      (I have wanted to say that since the beginning of this thread...)

      --Stak

      --
      Holy happy hippy crap!
    2. Re:He got paid. It's GPL. by corbettw · · Score: 1

      Given the way this guy is whining and begging rather than just doing something about it, I'd say MySQL is already forked.

      --
      God invented whiskey so the Irish would not rule the world.
    3. Re:He got paid. It's GPL. by gomek-ramek · · Score: 1

      He *has* forked it. Regardless of Monty's intentions, I'm growing tired of seeing this argument stated over and over.

    4. Re:He got paid. It's GPL. by greg1104 · · Score: 1

      The documentation is not GPL, a move defended quite weakly by Sun. That article does address one of the real reasons for what Monty is doing though: "MySQL forks should have their own, specific, documentation". Monty doesn't want to recreate all that from scratch, so forcing that into more open licensing would make his life easier.

    5. Re:He got paid. It's GPL. by montywi · · Score: 2, Interesting

      We have been working on a branch of MySQL, MariaDB, for 11 months already, so it's not like I am not doing anything.

      However, the problem is that with a bad owner of the MySQL copyright, a fork that can't survive for long (because no one will be willing to pay for development of it). This is why we put up the petition; To give all MySQL users a chance to get heard and help affecting that MySQL will be available for all also in the future.

    6. Re:He got paid. It's GPL. by Anonymous Coward · · Score: 0

      Don't forget there is always PostgreSQL!

  15. Hypocrite by Anonymous Coward · · Score: 1, Insightful

    Hypocrite Monty.
    Give back the billion dollars and we may talk.

  16. C'mon man... by raftpeople · · Score: 3, Funny

    don't Monty me on this deal!

    1. Re:C'mon man... by VGPowerlord · · Score: 1

      He should have kept MySQL instead of trading it for what was behind door number one!

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
  17. Dear Monty... by Richard_at_work · · Score: 3, Insightful

    If you had never sold MySQL to Sun in the first place, it wouldn't be in the position it is now in. I hope the money was worth it.

    Why are you so concerned now? Your chance to do something came and went, and so did you.

    Also, I rather think you overrate MySQL in that petition post, but thats just mho.

    1. Re:Dear Monty... by montywi · · Score: 3, Insightful

      I have answered your questions in my blog post here
      What we are now working on is just to ensure that MySQL gets a good home, which is of benefit for all MySQL users.

  18. There is already a perfectly good free DBMS by A+beautiful+mind · · Score: 4, Insightful

    It's called PostgreSQL. It's fast, what's even more important, it's correct and it's tried and tested. Get it here.

    --
    It takes a man to suffer ignorance and smile
    Be yourself no matter what they say
    1. Re:There is already a perfectly good free DBMS by up4fun · · Score: 2, Interesting

      And another in the wings as drizzle - a fork of mysql. This is getting a lot of attention and some parts are considerably cleaner and faster than mysql.

    2. Re:There is already a perfectly good free DBMS by BobMcD · · Score: 1

      It's called PostgreSQL. It's fast, what's even more important, it's correct and it's tried and tested.

      Can you elaborate on the 'correct' with emphasis?

      Google says that both postgresql and mysql get hits from 'incorrect results'. Are you stating that mysql's bugs have gone unfixed while postgre's have not? Or what?

    3. Re:There is already a perfectly good free DBMS by Anonymous Coward · · Score: 0

      to quote austin powers, why won't PostGres die already?

      10 years ago when I got into Linux it was a neglected project. 3 years after I started offering hosting I got one request for it, and when I explained that there wasn't much demand I got this little speech.

      Give up already. Use a standardized environment. Learn a new skill. Stop lecturing people. Drop your fetish for things that are unpopular.

    4. Re:There is already a perfectly good free DBMS by Anonymous Coward · · Score: 0

      Shun the non-believer. Shunn. Shuuuunnnnnah.

    5. Re:There is already a perfectly good free DBMS by Anonymous Coward · · Score: 1, Insightful

      > Use a standardized environment

      Windows it is then.

    6. Re:There is already a perfectly good free DBMS by Anonymous Coward · · Score: 0

      Well, for example, PostgreSQL is fully SQL compliant and MySQL is not.

      Also, please see this:
      http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html

      written by none other that Mynty himself.

    7. Re:There is already a perfectly good free DBMS by jedidiah · · Score: 2, Informative

      Sorry but all of your ranting reads more like a reason to dump mysql than postgres.

      SQL is that 'standard' environment. The fact that mysql now has yet another reason
      why discriminating users might shun it doesn't make all of those other reasons
      suddenly disappear.

      Fork mysql.
      Use postgres.
      Use a more embedded 'free' solution.
      Use a serious 'non-free' solution.

      There are genuine industry standards here. Where's the tragedy?

      --
      A Pirate and a Puritan look the same on a balance sheet.
    8. Re:There is already a perfectly good free DBMS by TheSunborn · · Score: 2, Insightful

      Correct as in
      If you insert "Hello world" as a date, it will not accept it, and convert it into "god known what". (This problem exists with all datatypes).
      If you use transactions on table that don't support it, it will not just ignore commit/rollback commands.
      If part of a transaction fails, a commit will not commit the rest of the transaction.

      And PostgreSQL got a much better query optimizer. I still can't use views in our MySQL database because mysql keep using the wrong index. (MySQL is really bad when optimizing queries where the select that created the view uses a key)

    9. Re:There is already a perfectly good free DBMS by sco08y · · Score: 4, Informative

      Can you elaborate on the 'correct' with emphasis?

      Google says that both postgresql and mysql get hits from 'incorrect results'. Are you stating that mysql's bugs have gone unfixed while postgre's have not? Or what?

      For fairness, I'm going by MySQL version 5.5, the development version.

      The default storage engine will quietly ignore foreign key constraints and transactions. source for default engine, claim that MySQL parses and ignores for non-InnoDB

      There are multiple "SQL Modes" that can alter correctness, source, but by default the DBMS doesn't try to validate input. It's pretty confusing what mode does what, and I don't care enough to figure it out, but MySQL's approach has always been Do What I Think You Mean, and if they set the new version to be ANSI compliant by default it'd break all the existing sites built on it.

      (I'm claiming this qualifies as "not being correct" by virtue of the Information Principle. Granted, SQL itself violates it in many ways, but MySQL proved that you can do worse than SQL.)

      PostgreSQL has a far more correct transaction model. In some ways, they're actually better than Oracle. (In Oracle, a DDL statement will start a new transaction, whereas PostgreSQL wraps DDL into a transaction.) For starters, there aren't multiple "storage engines" per table with different transactional behaviors. source, sort of.

      Also, PostgreSQL, to my knowledge, correctly validates input. It's kind of hard to cite a source for this since there's just no FAQ entry "Q. How do I configure PostgreSQL to silently corrupt my data? A. You can't." But by the same token, they don't have any long-standing terrible design decisions that they have to maintain compatibility with.

    10. Re:There is already a perfectly good free DBMS by Carewolf · · Score: 1

      PostgreSQL have been designed to be a correct database from the ground up. MySQL is only a strict database if you use the later fused-in InnoDB. The point is that MySQL was designed to be a fast storage engine, but not a true database. It is excelent for its original purpose but it makes a lousy database.

    11. Re:There is already a perfectly good free DBMS by friedo · · Score: 2, Informative

      mysql> create table blurb (foo datetime);
      Query OK, 0 rows affected (0.00 sec)

      mysql> insert into blurb (foo) values ("hello world");
      ERROR 1292 (22007): Incorrect datetime value: 'hello world' for column 'foo' at row 1

      No problems with invalid data types if you bother to RTFM and setup the config properly. (It's not hard. Just turn strict mode on.)

    12. Re:There is already a perfectly good free DBMS by Just+Some+Guy · · Score: 1

      3 years after I started offering hosting I got one request for it, and when I explained that there wasn't much demand I got this little speech.

      On behalf of competent hosts everywhere, I say this sincerely: thanks for the customers!

      --
      Dewey, what part of this looks like authorities should be involved?
    13. Re:There is already a perfectly good free DBMS by Sxooter · · Score: 1

      That's like a car that comes with the airbags in the trunk and if you install them properly you'll likely not die in a collision. Is it really that hard to make it do that all the time? It's easy enough to be disabled by the client on mysql as well. Reminds me of Bill Gates blaming most Windows crashes on users.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    14. Re:There is already a perfectly good free DBMS by greg1104 · · Score: 2, Informative

      No problems with invalid data types if you bother to RTFM and setup the config properly. (It's not hard. Just turn strict mode on.)

      Strict mode is a client setting, which means that you're always at the mercy of applications turning it off and inserting garbage. And there's the "IGNORE" keyword to allow that too. There is no way to make a MySQL server reject all incoming bad data.

    15. Re:There is already a perfectly good free DBMS by greg1104 · · Score: 1

      You'll find more references for what you're talking about Why PostgreSQL Instead of MySQL, and the associated Transactional DDL page goes over how it compares with Oracle--which has recently added a feature to address this area, so picking on it in this area is a bit out of date now.

    16. Re:There is already a perfectly good free DBMS by dissy · · Score: 2, Interesting

      There is already a perfectly good free DBMS
      It's called PostgreSQL. It's fast, what's even more important, it's correct and it's tried and tested. Get it here [postgresql.org].

      I'm confused on your suggestion. You want Monty to take PostgreSQL, change it's license to closed source, and sell it as a product?

      If not, I don't see why you would suggest it over MySQL, which is what he is trying to do that with currently.

    17. Re:There is already a perfectly good free DBMS by TheSunborn · · Score: 0

      But as the other said, the client can always change that setting, so it's not as usefull as it should be.

      And one thing I could never find out is, how do you set this on a shared web host, so all scripts no matter their source would obey it.

      My own mysql server which I use for development does in fact have all the strict settings enabled.

    18. Re:There is already a perfectly good free DBMS by sco08y · · Score: 1

      Thanks for mentioning that; I absolutely didn't know about the editions feature.

      It highlights, though, a big issue with Oracle: they have so many complicated features that their transactional model is incomprehensible. There's the standard commit, rollback and savepoints, then you have flashback, and you have the undo, and now you have editions.

      (I probably have some details wrong, but in my defense I'm more of a software guy than a DBA, and I'm just not that interested in learning all things Oracle. Great system, I just wish it would get out of my way.)

      From looking at the docs you linked to, I can see how it would be incredibly useful. Editions essentially allow the DBMS to allow multiple versions of the database. That's not what transactional DDL is though, and editions don't replace that functionality.

      I don't think Oracle is going to offer that feature, incidentally, because very few of their customers actually want it. You only need transactional DDL is when you need to modify your schema dynamically. (And if you think you can _correctly_ modify a schema dynamically without it, you don't understand concurrency.) In a typical Oracle setup you're encoding business logic in the schema and you virtually never need or even want to do that. Your database not only represents but literally is a set of legal and financial obligations. You're just not going to want to create new rules on the fly or, worse, have those things disappear without a trace.

  19. Baloney! He doesn't want to save MySQL by SwashbucklingCowboy · · Score: 4, Insightful

    He wants to build another business on MySQL and force Oracle into letting him do it.

    This is greed masquerading as virtue.

  20. Monty is a douche by thetoadwarrior · · Score: 3, Interesting

    He got his money and now he sees an opportunity to get his code back that he sold and the shyster is doing what he can to get it back.

    He has his own db, MariaDB and if it's any good then he shouldn't care since its whole purpose is that it's a replacement to MySQL.

    I've also noticed he's not allowing comments on his blog that counter his points no matter how mature and well presented they are.

    I really hope Oracle gets the ok, if for any reason to shit in this guy's Cheerios. I won't have anything to do anything he's working on.

    1. Re:Monty is a douche by montywi · · Score: 1

      If you read the petition and my blog, you should know that I am working on to find MySQL a good home and to ensure that MySQL is actively developed also in the future under Open Source. The idea is not to get the code back.
      If you would have read the published comments on my blog, you would see that there is also negative onces. I do not publish things that contains bad language, things already commented upon or questions that are already answered in the blog or in the comments.
      When it comes to MariaDB, I am committed to work on it and keep it Open Source.
      The problem is that with a bad owner of the MySQL copyright, no fork can keep MySQL alive forever. You can read more about this in my blog.. It's now, before the Oracle / MySQL deal is approved, that MySQL users has a last chance to affect the future of MySQL by signing the petition.. If you do nothing now, you don't have anything to complain about if and when Oracle would stop developing MySQL as Open Source.

  21. A sentence is missing from the beginning... by mark-t · · Score: 4, Insightful

    "In January, 2008, Sun legally acquired MySQL for $1 billion."

    1. Re:A sentence is missing from the beginning... by JWSmythe · · Score: 4, Insightful

          You have to provide references before saying something like that. :)

          It was $1B in total considerations, which most likely wasn't all cash. I'm sure all of it didn't go in Monty's pocket, but I'm sure he did walk away with a pretty nice sum.

          There's a thing about business though. Most places want to grow a business from nothing, to the point where it's a viable product to sell. Then they sell it. All of it. There's no looking back. It was yours, now it's not. So sorry, move on.

          If I made something, and it sold for $1B, I'd be a pretty happy camper. Hell, Sabeer Bhatia sold Hotmail in 1997 for $400M, and he was happy. Now (in a 2007 article I read), is funding new startups with the hope of making the next killer app that will be bigger than Hotmail.

          I have a few things that I've done, and if someone offered me even $1M to give one up, I'd take it. I wouldn't look back. I'd smile the whole way to the bank. :)

          If he wants MySQL back, tough. If Sun decides to gut it, and make the MySQL site into a porn link farm web site, and the database engine into a shell script that greps a flat file, so be it. It's theirs, and it's their decision. They could sell to Oracle, or Microsoft, or anyone they'd like.

          If he *really* wants it back, he should put his effort into his new database, and don't give it up next time, even for $1B.

      --
      Serious? Seriousness is well above my pay grade.
  22. Let's just use PostgreSQL by bogaboga · · Score: 1

    Why? Because the alleged shortcommings of PostgreSQL can be solved and it is far more superior to MySQL when it comes to supporting partial indexes. MySQL would not know how to handle this.

    1. Re:Let's just use PostgreSQL by Dan+Ost · · Score: 1

      Out of curiosity, what are the "alleged shortcommings" or PostgreSQL?

      I've never used PostgreSQL on any large project, but I'd like to eventually. If there are serious issues with PostgreSQL, I'd like to know about them beforehand.

      --

      *sigh* back to work...
  23. InnoDB is Oracle already.. by praseodym · · Score: 4, Insightful

    Since InnoDB (the only proper storage engine in the default MySQL distribution) is owned by Oracle already, why bother?

    1. Re:InnoDB is Oracle already.. by msimm · · Score: 2, Interesting

      You know he'd started the Maria engine because of concerns regarding InnoDB's ownership (Oracle bought Innobase Oy in October 2005) in 2007.

      --
      Quack, quack.
  24. Open Source is a new business model, but by Anonymous Coward · · Score: 0

    this look pretty much like many old cheats: My Sql was sold for 1 Billion dollars and now he would like to get it back.... for free.
    the real questions anyway, are others :
    Who would trust and donate code to a project managed by such a man ? ....and was Sun really so stupid to pay all that money for the mysql "brand" without asking any clauses ?

  25. Why the hell is anyone still listening to him?! by MikeRT · · Score: 1

    Seriously, you have to be a moron to take him seriously at this point. Anyone who is motivated to protect something like he claims to be in protecting MySQL does not sell off the rights to a multinational corporation, especially not one in constant turmoil like Sun has been for several years. If he wanted to protect MySQL, what he would have done is tried to turn the company into a non-profit like Mozilla.

  26. Read the petiton - it is not about Monty! by JohnMurtari · · Score: 1, Insightful

    Folks, I read the petition before commenting. There are options on what to do, and one of them is to release it to an independent entity "MySQL must be divested to a suitable third party that can continue to develop it under the GPL." That certainly doesn't have to be him. It does provide a very effective low cost alternative and I can't see Oracle putting a lot of effort into a competing product.

    1. Re:Read the petiton - it is not about Monty! by Anonymous Coward · · Score: 0

      Folks, I read the petition before commenting. There are options on what to do, and one of them is to release it to an independent entity "MySQL must be divested to a suitable third party that can continue to develop it under the GPL." That certainly doesn't have to be him. It does provide a very effective low cost alternative and I can't see Oracle putting a lot of effort into a competing product.

      Well everyone's issue IS that it's Monty asking this. If it was anyone else asking they would probably get a fair amount of sympathy. Basically Monty is asking, in effect, for that billion dollars from Sun to be a personal gift to him.

  27. Fuck Monty and the horse he rode in on by ReallyEvilCanine · · Score: 4, Insightful
    This three-week-old story hasn't changed a bit and neither has Monty's disingenuous hypocrisy.

    If he'd wanted to retain control then why did he sell mySQL to Sun? Once that sale was completed he gave up his rights and claims. He certainly didn't have a problem with a corporation owning it in exchange for a cool billion earlier.

    What Sun said they wanted to do with it is immaterial; Monty's rights to do anything more than complain vocally were terminated by his own hand the instant he signed the contract, and were made irreversible when he deposited that check.

    The fact of the matter is that Oracle doesn't give more than about a shit-and-a-half about mySQL. Oracle cares about Enterprise installations and mySQL not only ain't there now, it never will be. Even Foxbase^W^H MS SQL Server spanks it 37 ways to next Tuesday in Enterprise and Data Warehousing environments.

    Meanwhile, if mySQL really is and has remained open source, then it's still open, so Monty should STFU and fork it already. If not, then he himself killed it and there's no one else to blame.

    Once you sell your 2CV to someone, you have no more say in what's done with the car, even if it turns out to have been bought by Top Gear and they want to blow it up. Once you take the money, you don't get to complain anymore. If it had meant that much to Monty then why did he sell?

    Cake: have vs. eat.

    The comment moderation on his blog is just icing on that cake -- only comments supporting poor, ickle widdle Monty's untenable position are allowed through.

    And for those who still refuse to change the "evil Oracle" record, The base Oracle DB charge is $350 (Std) / $950 (Ent) per user or $17,500 (Std) / $47,500 (Ent) per processor -- annually, not including required support and other charges -- Oracle doesn't give a shit about mySQL and the paltry few thousand that supporting it might bring in.

    If it's really still Open Sauce and the community doesn't like what happens with it then mySQL will fork. Again. Except that it will need a new core team since the current core team has bills to pay and enjoys employment during an economic mess.

    1. Re:Fuck Monty and the horse he rode in on by dunezone · · Score: 1

      Its like Ebaumsworld. Created by a few people in the late 90s, years later they sold the rights to another company, were kept on staff and were eventually laid off. They released their own statements feeling that they were screwed, yet fully forgetting that they were paid off so they wouldn't have control.

    2. Re:Fuck Monty and the horse he rode in on by icepick72 · · Score: 1

      A cool billion the first time?! Obviously he wants it back to sell again! Simple math.

    3. Re:Fuck Monty and the horse he rode in on by Anonymous Coward · · Score: 0

      If he'd wanted to retain control then why did he sell mySQL to Sun?

      He didn't. He had already lost control before that deal went through. He had no say in it, and was only informed of it afterwards.

      He certainly didn't have a problem with a corporation owning it in exchange for a cool billion earlier.

      As a shareholder, he got a piece of that billion — probably a pretty healthy piece. But it wasn't all his money, or even most of it.

      Monty's rights to do anything more than complain vocally were terminated by his own hand the instant he signed the contract

      He didn't sign anything.

      Meanwhile, if mySQL really is and has remained open source, then it's still open, so Monty should STFU and fork it already.

      He did. But there's more to it than that. As he says in his blog, "(y)ou can fork a GPL infrastructure project, but not the economic ecosystem around it."

      The comment moderation on his blog is just icing on that cake -- only comments supporting poor, ickle widdle Monty's untenable position are allowed through.

      Uh, did you stop reading at the first comment? Monty has had to post many comments defending his position against the doubters.

      Read his blog post. He addresses everything you've brought up.

    4. Re:Fuck Monty and the horse he rode in on by Anonymous Coward · · Score: 0

      The fact of the matter is that Oracle doesn't give more than about a shit-and-a-half about mySQL

       
      i disagree. if oracle can turn even a small percentage of the MySQL install base into paying oracle customers, it's a huge win for them.

    5. Re:Fuck Monty and the horse he rode in on by Anonymous Coward · · Score: 0

      And for those who still refuse to change the "evil Oracle" record, The base Oracle DB charge is $350 (Std) / $950 (Ent) per user or $17,500 (Std) / $47,500 (Ent) per processor -- annually, not including required support and other charges -- Oracle doesn't give a shit about mySQL and the paltry few thousand that supporting it might bring in.

      Oracle used to offer Oracle 10g XE for free, even for production use, but I don't know if that now applies to Oracle 11g. 10 XE had limitations like 1 CPU & 4GB per DB IIRC, but that would hardly bother most people who might balk at Oracle's entry-level pricing. Most of those who wouldn't consider switching from MySQL would never pay up for Oracle anyway, and Ellison isn't subject to the peculiar stupidity afflicting the RIAA. And Oracle would be foolish to strangle MySQL - it's a good way to upsell some people into becoming paying Oracle customers. Oracle could enhance MySQL with Oracle DB interfaces to ease mixed installations and data migration (in the profitable direction, of course) to discourage use of PostgreSQL/Firebird/whatever, and they'd probably still break even on continuing MySQL commercial licenses.

      - T

  28. Buy it back by linuxgurugamer · · Score: 1

    So rather than ask for it back, why doesn't he offer to buy it back for the same amount that he was paid for it?

    This sounds too much like like greed to me.

    The choices on the petition are laughable as well. MySQL is already GPL. If Oracle does try to kill it, there is nothing to stop another company from forking it (aren't there several forks already) and providing commercial support & development. Asking Oracle to do work on it, and then release that work for free, is also stupid. Oracle is a company which wants to make money. Why should they develop competition to their main product and then release it for free?

  29. And how much money did he make from it? by frinkacheese · · Score: 4, Insightful

    So MySQL sold for a cool $1 billion in whatever it was, and now he wants to get it back for free? This is so funny it may just work.

    1. Re:And how much money did he make from it? by Anonymous Coward · · Score: 0

      Hey, it worked for the guys who built Skype. Why not take a page out of their play book.

  30. Monty NoLastName by Junior+J.+Junior+III · · Score: 1

    Wow, must be nice to be as famous as Madonna and no longer need a last name.

    --
    You see? You see? Your stupid minds! Stupid! Stupid!
    1. Re:Monty NoLastName by Anonymous Coward · · Score: 0

      His last name is Python. And this whole parrot sketch is getting a bit dead.

  31. Feel free OS by francodane · · Score: 1

    I think that this database must be free,but also more and more software,i'm going to the petition page

  32. Ah, so that's why he spammed me this weekend by paulhoffman · · Score: 2, Informative

    He apparently went through the database of everyone who had ever submitted a bug report and vacuumed up email addresses, because that's the only way he would have known me to send me his appeal. That's not stooping low: that's slithering.

    1. Re:Ah, so that's why he spammed me this weekend by Mad+Merlin · · Score: 1

      It can't have been all of them, I didn't get an email.

  33. No no no! by geminidomino · · Score: 1

    Having seen the date 1969-12-31 one time too many, I say let the fucker die.

    DIE DIE DIE!

    I hate HATE HATE HATE mysql.

    (why yes, I have recently been replaying FF VI. Why do you ask?)

  34. Sometimes I wish... by PerfectionLost · · Score: 1

    Sometimes I wish MySQL had less cheese in it.

  35. Save? by mseeger · · Score: 1

    It looks to me more like "I had to destroy MySQL in order to save it". He is (IMHO) not doing anyone a favor.....

    1. Re:Save? by toby · · Score: 1

      Have you been reading my journal? :)

      --
      you had me at #!
    2. Re:Save? by mseeger · · Score: 1

      Now i have :-)

  36. Monty Wants To Save MySQL by omar.sahal · · Score: 1

    Taking Monty at face value he seems to be saying Mysql was such a dynamic open source poject because of the way it was funded (a GPL codebase with a propriety licence for any one willing to pay), giving it lots of cash to develop (enabling full-time developers to work on the code base). Mysql (in Montys view) was not like Linux that had a distributed development effort behind it.
    Taking him at face value this seems to be a weekness in Mysql development model, the Oracle buy out is a case in point.
    Not taking him at face value however is Groklaw I think her assessment is a little harsh (not because I know Monty personally, I dont) as there is a reasonable explanation for his actions outlined in the Groklaw artical. He's trying to stop Oracle from Buying Sun and therefore mysql, as he can not see Oracle supporting mysql. Why would a company buy out a competitor, whose product makes less profit than theirs, and support it, even though it will take customers from their more lucrative products.
    I say this because with the accusations against Monty are strong and need to be proven in non contradictory ways.

  37. MySQL bad? Oracle worse. by Anonymous Coward · · Score: 0

    All of you who are mindful that MySQL is Sun's stuff, bought and paid for, and who are impugning the author of MySQL with ulterior motives, do not seem to realize that, however dark and dank the MySQL author's motives might be, Oracle's motives can only be worse and it has high-powered lawyers on retainer to back them up. If Oracle chooses to lock up the code of MySQL, a lot of database users may find themselves up the creek with no recourse whatever.

    1. Re:MySQL bad? Oracle worse. by Stumbles · · Score: 1

      Well your wrong about Oracle's ability to "lockup" MySQL... they cannot, at least not any of the GPLed code that is in there. So your point is moot, misleading and off base.

      --
      My karma is not a Chameleon.
  38. Who has shared hosting with PostgreSQL? by tepples · · Score: 1

    It's called PostgreSQL.

    MySQL has plenty of affordable shared hosting providers. What company do you recommend for hosting web sites based on PostgreSQL?

    1. Re:Who has shared hosting with PostgreSQL? by royallthefourth · · Score: 1

      Lithiumhas been a competent host for me. They've got MySQL and Postgres, and it's not too expensive either.

    2. Re:Who has shared hosting with PostgreSQL? by Anonymous Coward · · Score: 0

      I've seen a few small ones. They run Plesk and often offer Postgres aside MySQL.

    3. Re:Who has shared hosting with PostgreSQL? by uncledrax · · Score: 1

      Also, since it's been brought up before, there are 2 reasons my MySQL is as popular as it is in the webhosting world:
      1- it's free
      2- it worked easily/well enough when the whole Virtual-Server thing started taking off (I mean in Apache terms: 1 IP, 1+ web sites, not VMware terms :] )

      If MySQL dies, then web hosts will (slowly I'm sure) start migrating to using something else like PostgreSQL. Issues with either MySQL/Pgsql will be developed around, new management tools will emerge to fill the needs, and/or a new alternative will show it's head (someone mentioned a n existing fork of MySQL already).

      Dear Monty; Perhaps you overstate your usefulness. Pray I do no alter the deal any further. .. or something.

      If MySQL dies, it won't be the end of the Internet (I could only pray for so much to happen!).. I'm sure someone like Google would step in and offer consolidate database solutions.. does Gears or whatever already do that?

      --
      ----- The internet has given everyone the ability to have their voice heard equally as loud.. even if they shouldn't be
    4. Re:Who has shared hosting with PostgreSQL? by Anonymous Coward · · Score: 0

      I use a2hosting (as in Ann Arbor).

    5. Re:Who has shared hosting with PostgreSQL? by greg1104 · · Score: 1

      There's a list of PostgreSQL hosting companies available. Last time I was picking one A2 and hub.org made my short list; there are plenty of others too.

    6. Re:Who has shared hosting with PostgreSQL? by Anonymous Coward · · Score: 0
    7. Re:Who has shared hosting with PostgreSQL? by the_womble · · Score: 1

      MySQL has plenty of affordable shared hosting providers. What company do you recommend for hosting web sites based on PostgreSQL?

      Nearly Free Speech, Webfaction, Django hosting (they do PHP too) or Mythic Beasts. Virtual servers are also affordable these days.

      Between the above they cover everything from very cheap to as expensive as a dedicated server but worth it.

  39. What can SUN do? by gsgriffin · · Score: 1

    I'm not claiming to be an expert in this field, but have a simple question...

    If this is GPL, can SUN stop it from continuing to be GPL? Even if they purchase SUN, doesn't the GPL have to be maintained on software once placed in the public domain? Even if Oracle took it and if they stopped development of it, it wouldn't mean that the public would have to stop developing and using it, would it? Couldn't separate efforts, much like Linux, continue this on as if nothing happened, OR is this what can happen to any GPL in the future?

    --
    jsut athnoer menagiensls ltitle psrhae for you to dcoede. Why do we wtsae our tmie dnoig tihs?
    1. Re:What can SUN do? by Stumbles · · Score: 2, Informative

      Just to be clear, GPLed code does not equate to the same as "public domain". As for Sun, no, they cannot. Once code is GPLed it is GPLed. You are correct if Oracle took it over; they cannot stop development, if they tried to then Oracle would forfeit their use of the GPLed code.

      --
      My karma is not a Chameleon.
  40. pgsql is NOT FREE! by Anonymous Coward · · Score: 0, Funny

    pgsql is NOT Free Open Source! It is not GPL, so it is not truly Free. mysql is the only true community database and we must save it from corporate plunder at all costs!

    1. Re:pgsql is NOT FREE! by larry+bagina · · Score: 1

      If it's already free, why does it need saving?

      --
      Do you even lift?

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

    2. Re:pgsql is NOT FREE! by Anonymous Coward · · Score: 0

      Because Oracle realizes that true Free Open Source Software will eliminate their customer base once they realize that mysql is capable of everything Oracle can do. So Oracle wants to kill it and deny freedom to the community.

    3. Re:pgsql is NOT FREE! by Unequivocal · · Score: 1

      Oh shit! Apache's not free either. And crap, Ruby on Rails is MIT licensed. The sky is falling.

    4. Re:pgsql is NOT FREE! by aztracker1 · · Score: 1

      That presumes that mySQL can do anything Oracle can do, which is absurdly false. I don't really care for Oracle, but there is a lot it offers over mySQL (and vice-versa).

      --
      Michael J. Ryan - tracker1.info
  41. Re:Baloney! He doesn't want to save MySQL by Anonymous Coward · · Score: 0

    Give me an example of virtue that isn't a masquerade of one kind or another.

  42. Unclean Hands by Blackeagle_Falcon · · Score: 2, Insightful

    So, Monty uses dual licensing to turn his open source software into a profitable company, sells that company for a billion dollars, and now he's suddenly concerned with freedom. Oracle buying MySQL may be bad, but I don't think Monty has much credibility in opposing it.

  43. He's just a greedy hypocritical troll by tomhudson · · Score: 5, Informative
    Original source

    Background: MySQL is an open-source database used by millions. Originally developed by closely-held Swedish company MySQL AB, it was sold to Sun Microsystems Inc in January 2008. Sun is now in the process of being acquired Oracle Corporation. The deal is still awaiting European regulatory approval.

    Not happy with selling MySQL AB to Sun for a cool billion, Monty Widenius is now trolling regulators, the media, and anyone who will listen in his efforts to get back control of "his" database (without having to give back the money).

    European regulators still don't "get" the open-source software model

    The Europeans are holding up their approval of the Sun-Oracle deal because of concerns that the acquisition will reduce competition in the database industry. Oracle Corp, which is already the dominant player in large-scale corporate databases, already "controls" several open-source database products such as Oracle Berkeley DB and the InnoDB transactional storage engine for MysQL

    The reason I put "controls" in quotes is because it's very difficult to actually exert full control an open-source project, especially one that is licensed under the GPL or similar open-source license. It would probably be more accurate to say that Oracle "sponsors" both BerkeleyDB and InnoDB.

    It's all about being an unabashed hypocrite

    Widenius was originally able to control MySQL by insisting that the copyright for all code contributed by outsiders be assigned to MySQL AB. By doing this, Widenius was able to "dual-license" MySQL, with both a free GPL version and a paid commercial version.

    This licensing scheme was good enough when Widenius was in control of MySQL AB, but now that Oracle is buying Sun, suddenly Widenius wants both the licensing scheme changed to something that would allow his new company to sell modified copies without having to release the source code for their changes, and to have Oracle turn over control of MySQL to someone other than Oracle - perhaps the EU should consider (nudge nudge, wink wink) his new company, Monty Program AB?

    Calls the GPL licensing scheme an "infection", wants the EU to violate international treaties

    You can read more about the attempt to get the Europeans to retroactively change the licensing scheme from the GPL to something more "Monty Widenius-friendly":

    We would like to draw attention to the fact that some major concerns about the effects of the proposed transaction could be somewhat alleviated by requiring that all versions of MySQL source code previously released under the GPLv2 license (whether in a General Availability, Release Candidate, Beta, Alpha release, or as public bazaar or bitkeeper revision control trees) must be released under a more liberal open source license that is usable also by the OEM users and would also create an opportuity for other service vendors to compete with offerings comparable to MySQL Enterprise.

    In other words, he wants the European Union to violate Articles 9 and 12 of the Bern Convention on Copyrights and retroactively change the license from the GPL, which requires him to share any changes he makes to source code covered by the GPL, to a license that would let him take from the original authors, but not give back anything in return.

    The "copyleft/infection" principle of the GPL license represents a particular obstacle not only to revenue generation by the fork vendor but also to the overall adoption and market penetration of MySQL, MySQL forks and MySQL storage engines....

    When we were kids, our parents told us "share and share alike." The authors who contributed source code under the GPL adhered to this principle. If you don't want to share your changes, simply don't "borrow" their

    1. Re:He's just a greedy hypocritical troll by Anonymous Coward · · Score: 1, Insightful

      Widenius is hoping that Oracle will cave in because the delay of the Sun acquisition are costing Sun an estimated $100 million a month, and the uncertainty is damaging to both companies

      Monty is an insignificant buzzing gnat and couldn't delay things by an hour. It's SAP that gets to gum up the works. Heck IBM is probably in on the fun too.

  44. There are *many* open source RDBMS by toby · · Score: 1

    Others include

    And there are many more, relational and non-relational, out there.

    --
    you had me at #!
  45. I wonder by Dunbal · · Score: 1

    So exactly how many times are we going to have to read this same story again?

    I have no sympathy for Mr. Widenius - after all he sold MySQL to Sun for a nice chunk of change. If you don't like it, FORK IT. But shut the hell up already.

    --
    Seven puppies were harmed during the making of this post.
  46. It was sold by Anonymous Coward · · Score: 0

    He made his choice: he took the cash. If he wants to change his mind, he can buy it back.

    Perhaps Monty has never seen the show "Let's Make a Deal"? If the curtains open on your choice of door #1 and you've discovered you won the goat, it's too late to bargain.

    Or, if it was the host that opened the door on the goat, he could switch his choice and pick door #2 (postgresql), which might be a better deal.

    1. Re:It was sold by larry+bagina · · Score: 1

      I heard Mighty Wide Anus likes goat sex.

      --
      Do you even lift?

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

  47. It seems to be GPL so . . . so what? by pugugly · · Score: 1

    For all the crying about Monty's disingenuousness, Wikipedia shows the main license is still GPL, with a proprietary license available but not the only license. Presuming this is accurate (And I concede, I don't know exactly why anyone would pay a giga-buck for a GPL'd application given the inherent limitations on monetizing it in any way anyone else with access to the source could. I also don't entirely understand why one would buy a proprietary license for a GPL product? So finding out I misunderstand the situation would hardly be a shock.), um - so what. Phoenix the name, keep the code, fork the project - Oracle seems to be buying the mark, the code is open.

    So, uh, who cares. The GPL is a valid license, in order to actually grab the code itself Oracle would have to file a lawsuit and retroactively 'un-GPL' it, and given the (intermittently tested, but consistent) record of the GPL as a perfectly valid license, I don't see that happening.

    So . . . What am I missing that this sale is a major issue from the open-source pov?

    Pug

    --
    An Invisible Entity of Vast Power whose existence must be taken on faith alone: Liberal Media
    1. Re:It seems to be GPL so . . . so what? by frinkacheese · · Score: 2

      Yeah so what is the issue here? What exactly is Monty trying to rescue? Does MySQL contain any IP that Oracle owns that is not covered by the GPL code license?

    2. Re:It seems to be GPL so . . . so what? by vlm · · Score: 2, Informative

      I also don't entirely understand why one would buy a proprietary license for a GPL product?

      Read the GPL. It specifically prevents a variety of antisocial activities like not releasing the source code, not releasing it as a part of a non GPL program, etc.

      If you can buy the same code under another license that basically has no obligations other than "send us the money", then you have ... no obligations, which can be convenient primarily for anti-social folks. Dual licensing is basically the equivalent of the catholic church selling indulgences, its OK to sin, if you send us some cold hard cash.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    3. Re:It seems to be GPL so . . . so what? by SnarfQuest · · Score: 1

      If he gets it back, then he can sell it again for another billion to someone else, like Oracle.

      A billion here, and a billion there, and soon you are talking about real money.

      --
      Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
    4. Re:It seems to be GPL so . . . so what? by phantomfive · · Score: 1

      Yeah, actually; apparently there are some plugins and add-ons that MySQL (the company) used to sell, that aren't covered by the GPL. I think those are the things he really wants.

      --
      Qxe4
  48. Postgres is a superior alternative by Anonymous Coward · · Score: 0

    Anyone who is worried about MySQL should try postgres. If you've written your app correctly you can probably switch over seamlessly.

  49. Re:Baloney! He doesn't want to save MySQL by blueZ3 · · Score: 1

    The easy kind?

    --
    Interested in a Flash-based MAME front end? Visit mame.danzbb.com
  50. Re:Baloney! He doesn't want to save MySQL by gabereiser · · Score: 0

    He wants to build another business on MySQL and force Oracle into letting him do it.

    This is greed masquerading as virtue.

    took the words right out of my mouth...

  51. So far, approx EUR 16 million. by toby · · Score: 2, Informative

    He explains in the related blog post that the founders (presumably meaning Widenius and Axmark) received "less than 12% of the deal", which is quite believable.

    The EUR 16 million figure is from Widenius' Wikipedia entry. (Which is famously served by MySQL.:)

    In any case, this large lump of cash is only about half what Sun or Oracle would spend on MySQL R&D in just one year, and obviously a small fraction of what would be needed to buy it back - especially after the sale to Oracle is concluded, and assuming the new owner wants to sell.

    --
    you had me at #!
  52. OMG tehy r killin my BABY by Just!nVix · · Score: 2, Insightful

    Sooo, To understand the basics here...
    Monty wants to keep the internet free, and that is somehow connected to his old, crappy product being "freed" from the rightful owner. Uhuh, riiiiight.

    I read the tripe of a blog-entry, and I am disgusted. This man seems to write as bad as he codes. Aside from quite healthy competition, PostgreSQL comes to mind. Especially the feature of stored procedures (don't bitch, I am sure they included that after Monty sold it.)

    First and foremost, I need to point out the painfully obvious:
    The Infrastructure of the Internet is NOT free. The pipes are owned by companies, and they can rightfully charge for the usage. No second-rate celebunerd can change that. You have to be be BONO to be recognized beyond a casual /. entry, and even the glorious Number 2 (southpark reference) has problems with his logic on property rights (when it suits his coffers).

    To add to that, Oracle, in all their evil splendor, has the complete right, if it owns SUN, to modify, improve, abolish any and all property that came with the purchase. Who knows, maybe they will turn MySQL into something usable by serious programmers! Oh, wait, they HAVE a product, closed source, that has been established to work for decades, and that profitable companies pay good money for when it comes to managing data... I am shocked and awed!

    I know this is a very difficult thing to understand for you young freetards out there: Stuff costs money. Things and services. Like iPods, cleaning cars, using the turnpike, going to the pool, beer, hookers, and other fun stuff.

    And again, why is there no concerted effort to produce a GOOD product? MySQL can go away tomorrow and no one will give a flying rat's ass. Your SQL statements will still work, and all those young PHP coders will flock to competitors that suits their freetard mentality.

    Maybe someone can explain to me that whole FREE mentality. Somehow, everything has to be free if you WANT it. And then what? The pattern keeps emerging that those pining for the FREE fjords fail to differentiate other people's work from theirs. Others should provide free tools, free software, free this free that. But somehow, they want to charge for the result of using said tools.
    That, Gentlemen (and those high regarded few Ladies), is the problem here.

    I call Monty in reference to a Family Guy episode: HE IS A BIG FAT PHONY
    _______________________________
    ... Now, keep sending those letters.

  53. Because by toby · · Score: 2, Interesting

    Oracle actually wants it, and it's worth 10-100x what Monty could personally afford.

    --
    you had me at #!
  54. The best part of this... by rickb928 · · Score: 2, Funny

    .... is the preposterous idea that Sun and/or Oracle care a whit about online petitions or email campaigns.

    Unless Monty is just indulging in a popularity survey. In which case he forgot to ask us how we 'felt' about this.

    I, BTW, feel like you've gotten your money and want your cake back as well. Good luck. Fork it and compete with your previous employer, ok?

    sheesh.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
    1. Re:The best part of this... by Anonymous Coward · · Score: 0

      Well then, someone should start a petition campaign to tell him to STFU.

  55. given that he sold it, and for mucho money by obarthelemy · · Score: 1

    i find his political bid to try and get it back rather greedy.

    --
    The Cloud - because you don't care if your apps and data are up in the air.
  56. He's also spamming by e-mail (IMO)... by Anonymous Coward · · Score: 1, Informative

    He definitely learned some new tricks so it seems. On my company e-mail address I got the following e-mail, and I can assure you that I did not apply to be kept informed about MySQL on their website. Maybe a post on a mailinglist or two, but thats it. Nevertheless, I received the following e-mail:

    Hi!

    I am contacting you because you have in the past shown interest in
    MySQL and from that I assume you are interested in the future
    well-being of MySQL.

    Now you have a unique opportunity to make a difference. By signing
    the petition at http://www.helpmysql.org/ you can help affect the
    future of MySQL as an Open Source database.

    You can find more information of this on my latest blog post at:
    http://monty-says.blogspot.com/2009/12/help-keep-internet-free.html

    Help us spread the world about this petition!
    http://www.helpmysql.org/ is available in 18 languages and every vote
    is important, independent of from where in the world it comes!
    If you know people that are using MySQL, please contact them and
    ensure they also sign the petition!

    Regards,
    Monty
    Creator of MySQL

    PS: If you already have signed the petition or know about it, sorry for
            reminding you about this! Because of the importance of this issue,
            I am trying to contact every person that I have ever communicated
            with regarding MySQL.

    One has to wonder...

    Because I do care about MySQL but don't care for this petition I visited the website, read his blog (the least you can do is hear someone out) and wrote a somewhat cynical but polite comment how I felt about this action. Surprise; surprise; it never appeared on the (moderated) blog responses. And thats where I have to wonder if he's doing his best for a decent and honest attempt to help MySQL or if he's working out an hidden agenda...

    I for one don't think this is doing the good reputation of MySQL any good.

  57. Re:Baloney! He doesn't want to save MySQL by TooMuchToDo · · Score: 1
    Yeah, but when you hate Orcale, you can't really blame him

    /hates Oracle

  58. Didn't he get a billion dollars? by tjstork · · Score: 2, Insightful

    I'm sorry, but Monty sold his baby, and got well paid for it. If I could sell any program I wrote for a fraction of what he sold MySQL for, and they kicked me out of working on it, I could do any number of any other things I wanted to work on in life. Come on Monty, attack P=NP. It's not like you need a job.

    --
    This is my sig.
  59. sorry but I don't get it - just fork it by OrangeTide · · Score: 1

    In the event of Oracle funny business. What stops anyone from starting a new project, let's pretend it is called "FreeSQL" to avoid trademark issues. Which continues to enhance and releases the current version of MySQL, which is already open source. You can't undo open source of versions already released, the license has no provisions to do so.
    If there are patent issues then I guess that teaches all a lesson about bothering to file "defensive patents", unless they are assigned to some organization that cannot be easily sold or liquidated(FSF perhaps?). And simply publishing the patent information without filing is sufficient to block the creation of patent in that specific event, but not useful in a "defensive" patent trade. Of course defense of patents can be handled through copyright strong arming, for example an open source license that has a poison pill for patent litigation. Such a license might be worth considering for future projects, Ms-RL comes to mind as an example.

    --
    “Common sense is not so common.” — Voltaire
  60. Question by rudy_wayne · · Score: 2, Funny

    If Oracle cuts MySQL loose, does Monty have to give back the billion dollars?

  61. It doesn't matter. Fork it. by mmell · · Score: 2, Informative
    I mean, it's (still) just another open source project, isn't it? Fork it.

    And fork you too, Monty/Sun/Oracle.

  62. Time to switch... by XB-70 · · Score: 4, Insightful
    Instead of whining, it's time to make the switch to a 'real' database: PostgreSQL - http://www.postgresql.org/

    It may not be as fast as MySQL, but it's certainly more robust and capable. If you look at the core of ORACLE's design (which is pretty damned good), you'll find that Postgresql has similar design principals.

    When it comes to data loss, I'd rather the more robust database than the fastest one.

    --
    *** Don't be dull.***
    1. Re:Time to switch... by Blakey+Rat · · Score: 1

      If you could talk Dreamhost into doing that, it would be awesome.

    2. Re:Time to switch... by Just+Some+Guy · · Score: 1

      It may not be as fast as MySQL

      ...but it'll probably be a lot faster, especially if you're running more than one query in parallel. Seriously, PostgreSQL scales much better than MySQL, and that's pretty crucial when almost no one makes single-core server hardware anymore.

      --
      Dewey, what part of this looks like authorities should be involved?
    3. Re:Time to switch... by Issarlk · · Score: 1

      It certainly runs faster than a crashed MySQL.

  63. No, try some REAL slashdot terms by A+nonymous+Coward · · Score: 2, Funny

    It's like you broke up with your car and then go crying it back when it has found a new owner, while you're having no luck finding another car.

    It's like you broke up with your parents and then go crying back when they have found a new tenant, while you're having no luck finding another basement.

  64. Why keep being abused? by Anonymous Coward · · Score: 0

    In his blog he calls upon the MySQL users to "Help keep the Internet free" by signing his petition.

    Internet Freedom has nothing to do with MySQL.

    And really, given the past treatment - why bother with MySQL? Other choices exist.

  65. We Don't Need No Stinking Petition by mpapet · · Score: 3, Informative

    1. MySQL would need to be a sufficiently revenue-producing entity in order for it to sustain internal development at Oracle. What those revenue producing metrics are is impossible to know from the outside. I'm a pessimist though and would estimate whatever MySQL dev is done in-house will probably get chopped by 2/3 in order to make the revenue fit into their financing targets. That's assuming Oracle doesn't abandon it right away.

    2. This $1 Billion number being thrown around is a PR number. I'd guess Monty's gotten 10's of thousands of dollars for closing the deal. Other than that his payout won't come. He won't get paid because the value of the deal is typically based on payouts based on future earnings. We know Sun couldn't turn it into a bigger revenue producer. With the change in ownership, I'm sure Oracle will renege on whatever deal he had with Sun and tell Monty to "Go pound sand. Your issue is with the Sun Officers who signed the deal, not Oracle."

    3. I bet he's got a non-compete that prevents him from directly starting something. Which, Oracle would enforce while pretending about other parts of the agreement. That's why he's got this petition thing.

    Monty pretended those future payouts would work, got screwed by Sun, and now he's trying to get back in the game.

    Today's entrepreneurial lesson: get paid today, not tomorrow.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:We Don't Need No Stinking Petition by A+beautiful+mind · · Score: 1

      This $1 Billion number being thrown around is a PR number. I'd guess Monty's gotten 10's of thousands of dollars for closing the deal. Other than that his payout won't come.

      "Due to selling MySQL to Sun, Widenius earned about 16.6 million EUR in capital gains in 2008 (16.8 million EUR total income), making the top 10 of highest earners in Finland that year. (wp)"

      16.6M EUR is a tad more than tens of thousands of dollars.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    2. Re:We Don't Need No Stinking Petition by toby · · Score: 1

      MySQL would need to be a sufficiently revenue-producing entity in order for it to sustain internal development at Oracle

      A MySQL owned and developed by Oracle would make for some decent competition for SQL Server, wouldn't you think? It's probably easier to position MySQL like that than their traditional product (which tends to be associated with high costs, at least in minds).

      --
      you had me at #!
  66. Berkley DB by theManInTheYellowHat · · Score: 1

    Oracle has owned Berkley DB and Sleepycat since February 2006 and it is still in fine shape. Still open source and still used the same as it ever was. I suspect that MySQL will be the same.

  67. Fuck Monty and the whore he rode to Sun... by FlyingGuy · · Score: 0, Troll

    to collect his filthy lucre. I mean it, I really I do. I as as much a fan of FOOS as anyone and I cheer those who work their asses off to make it possible, but this guy is nothing but a greedy schmuck.

    CmdrTaco this is nothing but a blatant RGA © 2010 (Revenue Generating Article) and you are an asshat for even posting it. Yes you may have started /. but now you are abusing it.

    Monty, take your money and go have a great big mug of shut the fuck up you disingenuous little weasel.

    --
    Hey KID! Yeah you, get the fuck off my lawn!
  68. Oracle keeping MySQL might be worse by rednival · · Score: 2, Insightful

    Killing MySQL is not what we should be concerned about. Oracle taking control of MySQL's direction is a far greater danger. It will be harder to build a new community around a fork if MySQL still exists. If Oracle kills MySQL, a new fork will appear overnight and people will flock to it. If they keep MySQL around and do everything in their power to control it, Oracle can virtually ensure that MySQL never becomes a real threat to its proprietary database. My guess is that Oracle will keep MySQL but they will position it as a lightweight database server for small to mid-size databases. They'll push people toward their proprietary database for a "REAL" enterprise database.

  69. If you wanted it saved ... by Anonymous Coward · · Score: 0

    then you shouldn't have sold it to Sun in the first place, dumb-ass. This sets a bad precedent - get some company to buy you open source product for a tidy sum of money, and then back-pedal and start a petition to have it return to open-source.

  70. What an idiot! by AlexLibman · · Score: 0

    He sells his joke of a database product to Sun, and now he wants Mommy Government to hurt two large companies and millions of their customers, employees, and investors just to push for some socialist political agenda! Hasn't he ever heard of forking?! Viral license or not, Oracle and Sun are not Monty's slaves!

    Them GNU idiots are a cult, and rational people are right to stay as far away from them as possible. Good thing even before I knew anything about software licenses I was smart enough to specialize in PostgreSQL and SQLite based on their technological merits, which make MySQL look like a toy for retarded toddlers! Why anyone would use MySQL over PostgreSQL is beyond me - must be further evidence of the socialist bias in the open source community...

    If the Sun-Oracle deal goes through, I swear, I will rewrite every piece of software myself from scratch rather than resort to using anything with a copyleft license ever again!

  71. Derivative works by dhTardis · · Score: 2, Informative

    Personally, I feel the most reasonable interpretation (from the standpoint of being consistent and, well, logical) would be that linking does *not* create a derivative work (for example, is Firefox a derivative of the Flash plugin, or Flash plugin a derivative of Firefox? Seems to me they are fairly independent works that use the mechanism of dynamic linking to work together.)

    No one claims that Firefox is a derivative of Flash, or vice versa. What is claimed is that the resulting memory space with both objects loaded is a derivative work of each, which can only be created with the license-granted consent of the copyright holders of both objects. The trick: how strong is this argument since it applies only to the ephemeral address space created at runtime by the user and not, say, by Mozilla or Adobe?

    In the obvious case of MegaCo distributes foo that always links dynamically to libgpled.so, one can argue that MegaCo is effectively creating that combined object because there is no other way that their software could be used. But IANAL, of course, and I think the real lawyers (and judges) haven't fully settled the question.

  72. Y2.01k slashdot timewarp bug by Anonymous Coward · · Score: 0

    IPv4 exhaustion, various university pet projects seeking disruptive replacement of the Internet in a bid to hoard attention and I sold out MySQL please shed copious tears for me.

    Is this the matrix did the same cat just run by twice?

  73. Simple Solution by Stregano · · Score: 1

    If he wants it back, why can't he just give the money back that he sold it for? That seems simple enough.

    --
    The world is how you make it
  74. Maybe he realized money isn't everything... by Anonymous Coward · · Score: 0

    Say what you want about his potential greed, MariaDB and looking for a business angle, etc. IMO, it is possible that the $1,000,000,000 (or whatever he actually pocketed) isn't as satisfying to him now that he sees his life's work being flushed down the toilet by Sun's sale to Oracle. You have to consider that maybe, just maybe, this isn't all about money to him.

  75. Hey, Monty! by dwiget001 · · Score: 1

    Stop your whining.

    That is all.

  76. It's pure love by ClosedSource · · Score: 1

    Isn't more like you sold your girlfriend to another guy and he sold her to another guy and you want people to sign a petition to free here from guy #2?

  77. Clueless? by ClosedSource · · Score: 1

    "Basically Monty fell into the classic pitfall technical people with great ideas fall into."

    I'm not sure if MySQL qualifies as a "great idea", but how clueless do you have to be to not understand the VCs are in it for the money?

    Do people actually sign contracts covering their dream project without reading them or consulting a lawyer?

    1. Re:Clueless? by Kagato · · Score: 1

      The problem is you assume there is some clause in the contract that says the investors are going to try to take your company. There simply isn't. The fact is whenever you give people a significant interest in a company, even if it's not anywhere near a controlling share, they have legal rights. Taking over a company from the founder is about carrot and stick legal maneuvering not gotcha' contracts.

  78. Search overload by tepples · · Score: 1

    If I could query Google for shared hosting providers that offer PostgreSQL ORDER BY price, or shared hosting providers that offer PostgreSQL ORDER BY review score, I'd agree with you. But Google just isn't that advanced yet; one has to spend time looking for reviews of each provider one at a time. Having people with experience in the area narrow down the list of decent hosting providers saves everyone's time.

  79. Monty needs to put a sock in it... by TemporalBeing · · Score: 1
    See here and here for the reasons why. To summarize:
    • Monty made MySQL; licensed it under a dual license (GPL + MySQL Commercial License)
    • dual license structure worked well for MySQL AB - prevented commercial competitors, fostered community around GPL version
    • Monty sold MySQL AB to Sun for $1B without changing the license. No compliants; he worked for Sun.
    • Sun seems to be under the gun and going to get sold off - Monty quits, tries to fork MySQL as MariaDB. Wants to build a new "MySQL AB" under another name; but the dual license prevents it.
    • See opportunity to force Sun to change the license so he can keep his money from the sale, while still getting all the code, possibly also the commercial code, and redo MySQL AB
    • Monty's looking to do a "rinse-repeat".
    --
    Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
  80. VACUUM! (n/t) by toby · · Score: 1

    n/t

    --
    you had me at #!
    1. Re:VACUUM! (n/t) by jadavis · · Score: 2

      PostgreSQL 8.4 supports partial vacuum, meaning that old data usually doesn't need to be VACUUMed. That alleviates many of the complaints surrounding VACUUM.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
  81. MOD PARENT DOWN by VGPowerlord · · Score: 1

    Strict mode is a client setting, which means that you're always at the mercy of applications turning it off and inserting garbage. And there's the "IGNORE" keyword to allow that too. There is no way to make a MySQL server reject all incoming bad data.

    Strict mode is a server setting passed on either the command-line while starting mysqld (you know, the server daemon) or in its configuration file in the [mysqld] section, and only super-users (users with the SUPER privilege) can change it at run time.

    Hell, the page you linked to is titled "Server SQL Modes", which should have been a big clue that you were wrong.

    --
    GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    1. Re:MOD PARENT DOWN by greg1104 · · Score: 2, Informative

      Quoting the reference I linked to and highlighting the important bit:

      "You can change the SQL mode at runtime by using a SET [GLOBAL|SESSION] sql_mode='modes' statement to set the sql_mode system value. Setting the GLOBAL variable requires the SUPER privilege and affects the operation of all clients that connect from that time on. Setting the SESSION variable affects only the current client. Any client can change its own session sql_mode value at any time."

      Yes, you have to be the superuser to change the global mode. And the fact that it says "Server SQL Modes", but they're not really enforced by the server even if you change the defaults should a client decide to go sloppy, is exactly why this behavior is so shady. It's an example of exactly why the upthread idea of PostgreSQL trying to be as correct as possible by design from day one is so important--you can't just bolt this stuff on later and expect there to not be a hole left behind.

  82. Anti-petition by Lulu+of+the+Lotus-Ea · · Score: 1

    Is anyone conducting something to counter Monty's money-grabbing schemes. A counter-petition (in particular, one that got more signatures) that said "We FOSS developers oppose efforts (by Monty) to weaken or violate the protections of the GPL, and insist that MySQL code base remain free, and not be proprietarized by its former developers". Wording could be better, but something to that effect.

    I would sign in a second, and I suspect thousands of /. readers would too.

  83. Let it die by asamad · · Score: 1

    Just let it die. then we can all move to pgsql

  84. Re:its all in the name. by Dare+nMc · · Score: 1

    I still agree with the GP, The only thing that this sell could take away, is the right to use the name "MySQL." And possibly any updates that the new owners add to MySQL. IE we have the code in a GPL license, we can always build from that, we just have to choose a different name if oracle declares their branch of MySQL is no longer open-source. And also Oracle would become the only one capable of creating new MySQL pre-priority licenses of MySQL.

  85. Mod parent up! n/t by sgtrock · · Score: 1

    Title says it all...

  86. Want a free popular opensource project? by Nelson · · Score: 1

    I've suggested this before. Build PostgreSQL and package it with some tweaked configurations, enable all local connections by default, beef up the buffers and some of the memory usage by default, write some install scripts to make accounts for local users, add PLSQL out of the box... I can't help but think that that's like 80% of the problem the Postgresql holdouts have, you do have to do more lifting to get it running. Maybe start writing a Postgresql configuration GUI that will help you tune the config stuff some.

    If you want to be fancy include one of the replication packages out of the box too.

    Call it "MyPgSQL..."

    1. Re:Want a free popular opensource project? by larry+bagina · · Score: 1

      There are scripts to do schema conversion and stored procedures (functions) to emulate mysql functions but mysql has other non-standard functionality (like SELECTing columns which aren't GROUPed BY, DELETE ... LIMIT, INSERT ... ON DUPLICATE KEY UPDATE ..., silently truncating data, 2009-2-31, etc). Now, every sql db can be considered an extended superset of the SQL standard, but MySQL seems to be full of workarounds -- like a new column type for an updating timestamp vs using a trigger.

      --
      Do you even lift?

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

  87. Re:I'll think about it by HiThere · · Score: 1

    I'll think about signing his petition if he makes a legally binding pledge that the new product will be fully GPL3.

    Mind you, I still wouldn't expect the petition to get anywhere unless he also gave back the money, but it wouldn't hurt to ask for what I want. I just don't see any advantage in him owning things rather than Sun or Oracle.

    N.B.: Oracle is not well known as a friend to FOSS, in fact it's often a sponge on FOSS. But it's sure a lot better than an enemy.

    P.S.: Based on what I've heard, the thing to REALLY ask for is that the MySql documentation be made Creative Commons licensed. Who know, Oracle might just go for it.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  88. Re:I'll think about it by montywi · · Score: 1

    I am not out to buy MySQL, so I can't change the license. It's up to the new owner of MySQL to decide upon the license.

    The petition is about giving control to the MySQL users of the MySQL destiny. I have nothing to gain financially if MySQL is sold to someone else. My gain would only be that MySQL would have a much better chance to be available and developed under Open Source also in the future.

  89. The real problem with this was the GPL switch. by Spy+der+Mann · · Score: 1

    is the GPL and dual-license. When MySQL was LGPL, nobody had a problem with it. But then came greediness, the switch to GPL and the MySQL-AB demands for people to pay for just linking to the MySQL client (to date there's still no concensus on whether linking to the client is a GPL violation or not, but scaring small businesses into paying is really profitable).

    Frankly, I don't give a dime if Monty goes to jail, loses all his money or what not. What's really important is the ability for small businesses to use MySQL. With the Oracle-Sun deal, I really don't know what will happen.

    If we wanted to fork we'd have to use the 4.0 base which was LGPL. Any volunteers to re-fix who-knows-how-many bugs?

    1. Re:The real problem with this was the GPL switch. by TemporalBeing · · Score: 1

      This has nothing to do with LGPL and everything to do with Monty W. wanting a "Do Over" while keeping the money he raked in from Sun at the same time.

      MySQL being GPL + commercial license works very well. This was true even when it was LGPL + commercial license.

      Monty W. is only doing this petition b/c he first try failed - and actually got Oracle to make a very public statement about the continued support for MySQL as is with promise to the E.U; thus exposing his own greed.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
  90. no thanks by Anonymous Coward · · Score: 0

    I might give a damn if the product was worth a damn.

  91. Unfortunately, by toby · · Score: 1

    The SQL dialects are different enough to make the switch quite a lot of effort. Only applications designed for SQL portability from the beginning (a non trivial goal) would be the exceptions.

    --
    you had me at #!
    1. Re:Unfortunately, by Nelson · · Score: 1

      Yes that's true. I'm just thinking about making Postgresql a little bit easier to get going.

  92. Why? by toby · · Score: 1

    You don't need petitions to get water to run downhill.

    --
    you had me at #!
  93. You know... by toby · · Score: 1

    There might have been a *joke* in this thread somewhere. :)

    --
    you had me at #!
  94. But that's not how geeks work by SlappyBastard · · Score: 1

    If someone gave me a billion dollars, I would spend 90% of it building an orbital laser to blow up the moon.

    --
    I scream. You scream. I assume that means we're both acquainted with the problem. We proceed.
    1. Re:But that's not how geeks work by rbanffy · · Score: 1

      So he spent his billion, the laser does not work and now he wants another billion to try again? No way.

      Oh.. And that's no moon. It's a space station.

    2. Re:But that's not how geeks work by SlappyBastard · · Score: 1

      "And that's no moon. It's a space station."

      Everyone called me mad right up to the point we suddenly needed my laser!

      As for him trying again . . . I don't think he blew the money. I just think it is in the nature of geeks to not sleep peacefully while there is anything out there waiting to be tweaked a little better.

      --
      I scream. You scream. I assume that means we're both acquainted with the problem. We proceed.
  95. Some WTFs by Anonymous Coward · · Score: 0
    A couple of WTFs from the section "So what went wrong with MySQL 5.1 ?" at the Widenius article linked by the other AC:

    We have changed the release model so that instead of focusing on quality and features our release is now defined by timeliness and features. Quality is not regarded to be that important. To quote Mårten Mickos: "MySQL 5.1 will be release as GA in or before December because I say so". Mårten's reasons for this is that he needs something he can sell and a release marked "GA" is much easier to sell than a release marked "RC".

    The MySQL server team have a bug fixing policy where a bug that has existed a long time has a lower priority 'because people know about them'. This is supposedly one of the reasons why the Bug#989 mentioned above has not been fixed.

    The very first post is WTF-inspiring:

    knielsen said...
    Great post, Monty. Thanks for taking the time to write this, and thanks for still fighting for MySQL quality. Keep up the spirit!

    And another WTF post a little further down:

    Mark Callaghan said...
    MySQL Cluster _is_ carrier grade.

    - T

  96. How is that any worse than any other license? by bigtrike · · Score: 1

    How are any other licenses any worse? With BSD, you're under similar restrictions. With closed source, you're screwed. GPL allows you to fork the project as needed.

  97. GPL copyrights symbol names needed to link by bigtrike · · Score: 1

    When you link to a library, your compiled code must include the library's symbol names, which are supposedly covered by the copyright. Symbol names include function names from the library, and are necessary for the dynamic linker to work. The LGPL makes an exception for symbol names, so closed source can link against it. MySQL switched from LGPL to GPL specifically to try to make more money via a dual license. Whether or not this is enforceable is another story.

  98. Indeed by toby · · Score: 1

    When I think about "what comes (immediately) after MySQL," it really does look a lot like Drizzle.

    --
    you had me at #!
  99. Transact-SQL by tepples · · Score: 1

    And it could be abbreviated MSSQL

    Only if it gets improved to understand more Transact-SQL, such as the more flexible version of DATEDIFF that Microsoft SQL Server Express implements. (Having to integrate three systems that use MySQL, MSSQL, and SQLite is fun.)

  100. Header copied into the program by tepples · · Score: 1

    even though the library or exe *depends* upon the other work, it may not be a derivative because it does not *contain* the other work

    If the API's header contains an inline function or a C++ template, then this function or template instantiation gets copied into programs using the header. Is that a derivative?

  101. So, Oracle wants to kill mysql for what reason? by Ilgaz · · Score: 1

    What if Oracle figured there is a huge market out there which will never,ever use their products over MySQL because of their expensive, closed brand image and they will be happy to sell official MySQL support contracts to larger companies.

    I mean, God forbid, what if there is no conspiracy at all?

    Just 2-3 months ago, there was also a great conspiracy to kill Java, the company who relies their own damn products to that virtual machine purchased Sun to kill Java. Yea, right... Or, the evil plan to kill Open Office. Their only product in hand which competes directly and severely hurts Microsoft, the number 1 software house.

    Also, did someone check the size of Oracle, they are second largest software company on planet. If we subtract OS Business, they can easily hit number 1.

    A company sized as Oracle and has no "lets ship everything for our own windows" childish ideological obligations could really kill MySQL from "there", without paying billions. How? In couple of months, they could release some really working, perfectly solid, polished UI with dozens of Wizards "Oracle SQL Lite" for all operating systems with free support. Want to bet which solution would large companies, hosting providers would choose?

    Remember, it is 2010 now, Open Office exists and yet we still speak about MS Office.

  102. I don't think it's really about linking. by Estanislao+Mart�nez · · Score: 1

    I hope you have read this old exchange between RMS and Bruno Haible on whether CLISP had to be released under GPL if it was written to link to Readline.

    At one point, Bruno Haible asks whether he could avoid releasing CLISP under GPL by bundling it with a libnoreadline that he would write, which duplicated the interface of libreadline but offered none of the functionality. The end user compiling the program would the link it to the real Readline. This is the response RMS gave him:

    The FSF position would be that this is still one program, which has only been disguised as two. The reason it is still one program is that the one part clearly shows the intention for incorporation of the other part. [my emphasis]

    The way I read this is that the technical details of dynamic vs. static linking are just not decisive. The key questions come down to a judge's judgement call whether the part under dispute "incorporates" the GPL'ed work, and that the set of arguments that can be made in one direction or another is actually somewhat open-ended. So, for example, I bet you that if I wrote a debugger-like tool that allowed me to dynamically link into arbitrary libraries at runtime, inspect their symbol tables and call into their functions, nobody could make me release it under GPL if I distributed it together with a GPL-licensed library that was in no way needed for my program to work.

    The converse of this is that there are GPL licensors that take the position that some uses, despite not involving any linking at all, create a derivative of their own GPL licensed work. IIRC MySQL AB took this position with regard to client applications that used the GPL-licensed version of MySQL, even if the client applications did not link any MySQL-provided client libraries. In RMS's terms, these applications would "clearly show the intention for incorporation of" the MySQL server, by being written to rely on features unique to MySQL (e.g., by using MySQL-specific syntax or commands), or by virtue of only working if used with a MySQL server.

    As to why GPL Firefox can link to proprietary Flash, I'd suggest that a key reason why this is so is because no copyright holder that would have standing actually objects to it. Courts in the USA for the most part are only allowed to rule on actual disputes, and clearly it seems like none of the potential parties here have any dispute.

  103. Problems with MySQL by yuhong · · Score: 1

    Did you read this comment: http://monty-says.blogspot.com/2009/02/time-to-move-on.html?showComment=1233908220000#c6913688673838779641 I think the biggest problem was the business model of MySQL, which was based on support. And companies like Red Hat was supporting MySQL in it's RHEL, and they as a result did not use MySQL's support services. Thus MySQL had to make some features non-free. What is even worse, it looks like it was funded with VC, which means that either it had to IPO or sold to another company, according to this article: http://monty-says.blogspot.com/2008/01/sun-buys-mysql-ab.html I wonder what if Monty had chosen an IPO instead of selling it to another company? Seems that Monty was the CTO of MySQL AB, BTW.

  104. Re:I'll think about it by Anonymous Coward · · Score: 0

    Actually, if Oracle was forced to release mysql for free under a BSD-like style license, you'd benefit directly - you still have some goodwill from having developed previous versions, and your current work is quite similar.

    So, excuse me, but it doesn't look like you care only about mysql about users; actually it looks like you're caring mostly about yourself.

    Besides, mysql isn't so good or irreplaceable that the internet will die off without it. Sorry if you think otherwise, but maybe you should look away from the mirror from time to time.

    Cheers,

  105. Re:we don't really have a problem here by lagi · · Score: 1

    it's not "really" the death of "free internet" or open source software.

    you are right. as a freelance web developer, this don't mean much for me, if i develop right now something that use MySQL, that won't be a problem, cause the server will probably run the current free MySQL version.

    if worst will happen, and i won't be able to use an updated version of MySQL for free, i will just use PostgreSQL for new applications. my main development framework (CakePHP) has no problem with that.

    and MySQL will be forked anyway at need. what reminds me, didn't he (or someone) already forked it with some strange name?

    so from my point of view Oracle can go **** themselves, i just feel sorry for the big Companies, so i signed it of course.

  106. iirc by toby · · Score: 1

    They managed to sell while keeping critical parts to themselves. In MySQL's case, that ship sailed when Sun bought it.

    --
    you had me at #!