Slashdot Mirror


MySQL Ends Enterprise Server Source Tarballs

vboulytchev writes "The folks at MySQL has quietly announced that it will no longer be distributing the MySQL Enterprise Server source as a tarball. It's been about a year since the split between the paid and free versions of the database project. The Enterprise Server code is still under the GNU General Public License (GPL), and as a result MySQL appears to be making it harder for non-customers to access the source code. 'One of the things that many users worry about is whether they're getting an inferior version of MySQL by using the Community version. Urlocker says that MySQL "wants to make sure the Community version is rock solid," but admitted that the company has introduced features into the Community edition of the software that "[weren't] as robust as we thought, and created some instabilities." Because of that, the company is revising its policies about when features go into the Community releases.'" Update: 08/10 04:56 GMT by CN :While it is slightly harder to get, the source isn't closed by any means, so I updated the title to reflect that.

3 of 413 comments (clear)

  1. Official PostgreSQL fanboi thread here :-) by adnonsense · · Score: 5, Interesting

    My take: while MySQL has improved technically in leaps and bounds over the last couple of years, stuff like this (or having its transactional backends bought out from under it by Oracle) makes it increasingly difficult for me to recommend it as a business proposition to my clients. Meanwhile PostgreSQL continues to get the job done for the majority of my projects; I have a network of professionals who support it competently; and having followed the project since 2001 or so, I'm confident it's not going anywhere but forwards.

  2. Re:In related news by ShieldW0lf · · Score: 5, Interesting

    Wow...

    The same guys who lied about the suitability of their code for various purposes from day one

    The same guys who maintained that ACID was unimportant until the very moment they had it

    The same guys who have been setting this up for years with their Project Mayo/DivX Networks style licensing/contribution scheme

    You mean they actually went ahead and tried to use shady shenanigans to force developers who have no need for anything from their organization whatsoever beyond a copy of the community developed codebase to pay for access to the codebase?

    Wow. What a surprise.

    I made a decision to give preference to PostgreSQL over MySQL in my developments... not because of the technical merits involved, but because of the repeatedly demonstrated lack of trustworthiness of the MySQL team.

    I didn't expect to see my decision validated in such a rapid and undeniable fashion though.

    Just goes to show... technical skill is no substitute for good character or lack thereof.

    --
    -1 Uncomfortable Truth
  3. Re:Rock solid... Far from it unfortunately... by linuxwrangler · · Score: 5, Interesting

    PostgreSQL 8.2.4. :)

    Thank goodness I did my homework and selected PostgreSQL and not, as one consultant suggested, MySQL back when we selected the database for our application. I've never had it crash and on the few occasions where it was unceremoniously shutdown (accidental powerdown and such), it's always come right back up with no data loss. And it's just been getting better by leaps and bounds.

    --

    ~~~~~~~
    "You are not remembered for doing what is expected of you." - Atul Chitnis