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.
MySQL announced plans for a new BitTorrent based distributed backend.
After Bittorrent yesterday is this a trend that we should be worried about, or really just 2 separate instances?
-nick
Buh-bye... was fun while it lasted!
Look at ME! I'm MySQL! I'm a "real database!"
I don't suppose this is an attempt to get more money?
http://www.beanleafpress.com
Can we all just switch to Postgres now?
Cheap web hosting, I'm looking at you...
If moderation could change anything, it would be illegal.
Open Source may be an excellent model for developing software,
but I don't think it's a good business model.
As & when more Open Source businesses become a little
successfull, we will surely see some of them do what MySQL
has done.
I wonder how many other projects will start pulling this -- get the world hooked on your product, and then close the source after you reach a critical mass of commercial users who are likely to pay versus those who would be prone to forking and taking over open development. I think it's ignorant to assume people will just take the last open version and fork it to continue being free - there are commercial users who will likely be quite happy to deal with the closed version they trust. Hell - look at sourceforge -- they closed off their source, and do you see companies installing the GNU fork of the code internally? No - they buy the commercial sourceforge. It'll be interesting to see how many companies follow this trend.
http://mysql.bkbits.net/ is still there, and AFAIK it isn't going away anytime soon.
Il n'y a pas de Planet B.
If the enterprise edition is still under the GNU public license, how is it legal for them to close off the source code to the general public? From my understanding, when you use the GNU license you have to distribute the code with the binaries and cannot sell the code for profit.
Are they just selling as a service, or are they making profit from selling the code? Have i just mis-read the GNU license?
-Pizentios
Companies like redhat, SUSE, and even IBM are ALL suffering.
I prefer the "u" in honour as it seems to be missing these days.
... company is obviously designed to move people to buy the product that gives them more income.
This sounds just like the FUD that microsoft guy made by "admitting" that XP has problems in the hopes that people will move to vista.
I think it's best to simply ignore the marketing people. There are no "instabilities" in the stable community version above and beyond the normal cycle of bugs and bugfixes you see in any software.
MySQL versions 5.0.38 to 5.0.45 have had such major bugs that they have rendered themselves useless for a huge range of applications. Applications that use dates, or ones that expect the database to *NOT* insert random NULL values in a group by query.
I mean, even the most basic test suite would have easily caught these.
Here are just a few of the major ones:
Bug #28336
Bug #28936
Let me be the first to suggest UseToBeMySQL or NowItsNotYourSQL. Or better yet SoldOutMySQL. SQLMoneyWhore might not fly but then again offensive names don't seem to be a problem with open source (I'm thinking of GIMP).
These posts express my own personal views, not those of my employer
That's what competition is for.
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.
Before anyone bitches about it, this is perfectly legal. The GPL only requires you to provide source code to people who you also provide the compiled software to. You just can't restrict what they in turn do with the source code, which is why most GPL developers make the source code available to everyone and their dog.
"They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
It says that the source will no longer be shipped as a tarball. You now have to take it out of bitkeeper. IOW, you still get the source.
I prefer the "u" in honour as it seems to be missing these days.
It's right in keeping with the GPL. The GPL doesn't say "you have to give the source to all and sundry." No, they just have to give the source code to those they gave the binaries to, i.e., their paying customers.
The work-around for the community is hinted at here:
"Though MySQL AB will not be distributing the source tarball, Urlocker says that MySQL isn't going to try to stop distribution of Enterprise Server source by others. "If somebody wants to, that's fine. People can distribute it.... "
Getting the source code as a tarball on a public server for everyone is an intellectual exercize for the reader.
I read this as a "We're not going to be hosting for leeches. You want a public server, set your own up"
--
BMO
after all, it is called MY SQL, not your SQL, or her SQL.
"The folks at MySQL has quietly..." thats just awful, I know we don't read the articles... but we aren't even reading the first sentence of the submission now?
You can sell the code for a profit. That's the whole idea. I can literally take any GPL project and sell it for money. Nobody will buy it, but it is perfectly legal according to the GPL. Also you can buy the GPL software I sell you, and distribute it for free, which is also okay under the terms of the GPL. You and I just need to include the source code, or make it available.
Now since MYSQL owns rights to the code, they are also free to change the license at any time, though the currently distributed version are still under GPL.
....is on PostgreSQL. Good stuff!
The Army reading list
There's nothing "closed" about the source to MySQL Enterprise Server. It's still under the GPL. MySQL AB is simply choosing not to make the source accessible from their ftp servers to the general public, which doesn't stop anyone else from choosing to distribute it themselves.
Lots of OSS projects use Mysql. If they want to take their ball and go home, so bet it. we can take a tarball and create OurSQL.
Come on people this is what OSS is all about. forking and starting a new project because the current project leaders became poopwads.
Do not look at laser with remaining good eye.
This is a common misconception. You CAN sell GPL code. The GPL specifically allows it. The only thing you must do is provide the source code (in one way or another) and the only thing you can't do is include additional restrictions.
As the other posters have pointed out, the copyright owner has the right to dual license the software (offer the software under more than one license). The GPL is not law, but an open ended contract. It is permission to copy the code if certain conditions are met. This doesn't mean that the copyright owner can give permission under other conditions as well.
On the other hand, who is the copyright owner of patches and bug fixes submitted to them? IANAL, but it would seem to me that this could be a legal problem. For example, Sun requires anybody working on/patching Open Office to have a record on file delegating copyright of patches back to Sun. If MySQL AB doesn't do something like this, how do they plan to fend off lawsuits? (frivolous or legitimate)
I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
A MySQL fork: "OurSQL" or something like that
or
A general shift to PostgreSQL... seems a lot of people are favoring that route.
I don't care which way it goes, the community will respond and MySQL will become irrelevant.
Why couldn't these have happened at the end of March? Linux, GCC and Emacs to close source would have been fantastic April fools followups.
I'm writing a framework for Windows Services and Apps in C#. I want to keep the source code to the libraries "commercial," and make the four sample apps I write to test it with LGPL3.
I own the copyright to everything. Can I do this?
(I know it's OT but I don't want to go register on a list just to ask one GPL question.)
"Fork you!"
Really, it's that simple when you have GPL software.
I am officially gone from
...the community version as a test bed for the enterprise version, which in that case it becomes clear that there is an imbalance or dismissal of the value of the community users, an abuse if you will.
The GPL was intended to remove such abuses. The GPL v3 is intended to do the same thing but in consideration of the fraud of software patents. But the point is clear, the GPL in general is to prevent abuses.
On the slip side, there is nothing preventing someone who has access to the enterprise version from making it available to the community users. Or would that be considered an abuse of a paying customer?
no, I've had enough of your bullshit! take this goddamn article down right fucking now and change the title you worthless fucking excuse for a yellow journalist! For fucksake you READ the goddamn article before you post it, I HOPE.
Fucking immune from moderation troll-assed motherfucker, I will sacrifice my "excellent" karma to bring you down! Anyone want to clue me in on what's going on there? And what all the yelling is about?
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
This is utopianfiat. Some tarball hacked my account. Disregard.
By discouraging people from getting and using the Enterprise version, I feel less and less safe deploying it myself. Less users = less chances to catch problems. Less code = less review = less security.
I'm about to deploy 4 MySQL servers for some serious volume and was strongly considering buying into an enterprise package, largely on the strength of their monitoring tool, but now I'm seriously thinking it's time to try Postgres.
"One of the things that many users worry about is whether they're getting an
2 5
inferior version of MySQL by using the Community version."
They already have SCO, how much more inferior can they get.
http://slashdot.org/article.pl?sid=05/09/04/17302
boycott slashdot February 10th - 17th check out: altSlashdot.org
I dont think anyone is really suprised.
PostgreSQL is still free and more powerful anyway so no great loss.
---- Booth was a patriot ----
They should rename it TheirSQL.
[[ DmD ]]
This is actually the tendence that worries me. These days many people (thankfully not everybody) think they have the RIGHT to get everything for free. One bitches because product X is not Open Source (Ohh what a crime!!!). The other bitches because X (which VERY GENEROUSLY was giving many years of hard work to people who don't even write a line of code) is taking their hard work back for Y reasons (yes, making a buck for many years of hard work is not a bad thing , you know)
Another funny thing: I was talking to a man here at work. The man is a a rabious defender of OS. He wouldn't touch a non- OS program, he almost cried when MS made a deal with Novell, he screams how much he hates Photoshop and how great Gimp is (just because is OS)... And guess what? He develops a very good backup solution for databases and he takes good money for it. He was having some difficulties adding features. Knowing how good of an OS supporter he was I had the nerve to suggest to him to open the source of his program. ARE YOU FUCKING MAD?- he said. DO YOU KNOW HOW HARD I WORK FOR THIS SHIT? AND I WOULD GIVE IT TO THE DOGS?....
Moral of the story. If you work hard for your work and wnat to share , so be it. If you want to get your work back iand this is posible, just do it. You have the right. people will bitch, people will call you a shit, people will hate you... And yet, the majority of them won't share a shit either giving the oportunity.
Making money is not a crime folks....
It's time to realise that Abble's products are the biggest abomination these days. Just say NO to the dumb iAbble way!!
Well, time to make the WeSQL community oriented fork. Fuck MySQL AB and its totalitarian ways.
The parent's point is exactly true. Richard Stallman was selling copies of Emacs, using his own words "making a living" out of it, and proudly gives it as an example of a business model built around Free Software. Claims that MySQL AB violates the letter or the spirit of GNU GPL by charging money for the Enterprise version of its product are false and ignorant.
MySQL hasn't been a project for a long time (if ever)... it's a commercial application that happens to also be GPL'd. The vast majority of the development is done by MySQL AB, and other than users there isn't really much of a community. I'm not saying this is wrong, but MySQL isn't a project.
FreeBSD provides a good (non-database to avoid the flamewar) counter-point. While there are some commercial contributors, there is absolutely no commercial control of the project. What control does exist does so in the context of a meritocracy.
That's scary. I have a FAPP server at home.
If moderation could change anything, it would be illegal.
It's interesting to see how the community often openly promotes and vehemently defends an "open" piece of software but if the software starts to "close" then all the problems start coming out and suddenly it's a piece of @#$! The robustness of software doesn't change with a philosophy. It's all the in marketing. I mean if MySql were still open then we'd see posts comparing it against Microsoft's software. Now for "some reason" they're equivalent in the garbage bin. I will remember this indeed.
If OOXML is ratified as a standard I'm going to start distributing my source code in it. Of course I will be sure to use one of its undocumented "features" to make sure the code is totally inaccessible to anyone not using my proprietary text editor, which conveniently you can purchase for a mere $2k.
When you look at the licensing - and how unnecessarily complex it is, how open to interpretation free use is, etc.
Then when you look at the the history of mysql ab - how they used to tell developers that they didn't need referential integrity, didn't need transactions, etc - until they had them.
Then when you realize that this is a commercial organization - a for profit company. Then it should be apparent where this is all headed: They're growing a user base, and hope to tighten up the licensing and pull the profits in tomorrow.
ya... they sure seem to be struggling with that whole open source thing and making money...
I would guess your confused about the origin and intent of bittorent. Things like Distros and FSW are exactly what it's originator had in mind. What Bram Cohen intended was to make a system where low bandwidth could be multiplied to work around a central server download system. I am pretty sure that Al Gore didn't think it would all be pr0n when he invented the internet. Considering he is married to Tipper. Ok the last part was a joke.
Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
... meh. SQLite is better for "toy database" problems anyway. It's fast, it's free, it's Free, and it's very compact. For a lot of applications where people use MySQL, it will fit in with just a few little changes.
Sod MySQL, SQLite is the future.
Zonk, try reading the titles.
From the article: "MySQL ends distribution of Enterprise source tarballs" The bold shows words you decided to ignore.
www.purevolume.com/martyd
now if it had been *Bill* that had invented the internet . . . :)
hawk, ducking again
No t-shirt :)
hawk
The issue isn't that they are keeping what they made. They didn't make it all since they used stuff others had contributed under a certain condition. That being Open Source. The open source model is that you let others help you build the software. To close the source they would have to comb back through the contributions of other people over the years and take out all OS code that is what they didn't pay for in-house. Otherwise they would have to rewrite a whole new system from scratch and walk away from the MySQL code base as it stands.
It's like getting divorced and your ex gets only the second floor and the garage.
Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
I am going to say that yes, you CAN make your app GPL even if it depends on your proprietary library. I base my answer on this FAQ entry:
L ibs
http://www.gnu.org/licenses/gpl-faq.html#FSWithNF
As you can see that does go against the philosophy of Free software. If you still have questions send an email to licensing@fsf.org. I have asked GPL questions to this address and have received prompt advice.
how about a centOS end run around this?
Grandparent poster said: "This is because any party who receives the binary is entitled to the source even if they didn't get it directly from MySQL AB."
:)
You replied: "And you, Sir, are not entirely correct. I cannot bend over MySQL AB by giving people binaries of MySQL."
But grandparent never claimed that you could "bend over" MySQL AB. He simply said that any party who receives the binary is entitled to the source. Which is true. If MySQL AB provided you with binaries and source, and you pass on the binaries, then they're off the hook, and you're on the hook, but that doesn't contradict anything that GP said. In fact, it was more or less his point. GP was entirely correct. And so were you, except where you claimed that he wasn't.
Meanwhile MySQL 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.
Fool me once, shame on you...
I wouldn't be surprised that people making large infrastructure decisions are going to think twice before making any long term decisions (longer than a few years) concerning "open source" projects based on the two big money grabs just this week.
I don't respond to AC's.
you heard me!!!!!
A disruption in communication can mean only one thing...Invasion!
http://www.infidels.org/library/modern/mathew/logi c.html
:)
I suggest you take particular note of the sections labeled "Argumentum ad hominem", "Converse accident / Hasty generalization", "The fallacy of accident / Sweeping generalization / Dicto simpliciter", "Fallacy of division", and "Ignoratio elenchi". "Plurium interrogationum" and "The "No True Scotsman..." fallacy" may also be relevant.
Of course, no true slashdotter would bother to use logical arguments, so I guess you must be a true slashdotter!
Shit. Imagine trying to make a living off a brilliant product like MySQL that you were part of. Those bastards. How dare they try and do that. They should stop and have a good think about all the ravings from people who never contribute a damn thing to Open Source, and very little to the universe in general, and change their tack.
disgusting!
love,
dave.
From what I can tell, the only real differences between Enterprise and Community is support. We run community version for major production databases with no issues whatsoever.
And we're not the only ones doing so. MySQL had really better re-think the whole thing, whats the point of offering Enterprise when 90% of shops are going to go with the free product.
Zonk, Zonk: 3P Plural nouns go with what verb tense? The course gets harder as we go along...
Development is programmable; Discovery is not programmable. (Fuller)
The last thing you want to hear about a DBMS is this line from MySQL: "the company has introduced features into the Community edition of the software that "[weren't] as robust as we thought, and created some instabilities"
This, among other reasons, is why we switched to Postgresql some years ago. MySQL was (is?) not even ANSI SQL compliant, at least when we were struggling with it.
If someone has a business that respects the GPL AND makes a profit, then it's good for all of us. Building a successfull business around free software isn't exactly the easiest thing; we should actually encourage companies that pull it off. A healthy - profit making - indistry based on the GPL will attract more big players, which will attract more users, which in turn will lead to more GPL'ed software and more freedom.
MySQL AB is respecting both the GPL and its moral purpose, on top of being able to compete financially with closed source, 'tradicional' businesses. That's a Good Thing(tm)
Steve Ol' Boy says: We did "quit fucking around"...
PostgresSQL. Even Firebird SQL is getting bigger. I like MySQL. I hope a "community" sticks around.
But good for MySQL. They have built an incredible following, all on a free business model.
Shameless plug alert: Game server control panel
And for everyone using MySQL as a half-way serious DB, there's Firebird and PostgreSQL
What do you think of Firebird? I've been thinking of downloading and trying it out.
FalconShould there be a Law?
Hey, it works for me -- all of it. I started with MySQL 3.23 a bunch of years ago. From nothing, I learned enough to build large simple systems and complex small systems. Now, I build complex large systems; you better believe I'm sticking with MySQL for the long haul -- and I have no problem paying for it. I'm a business making money, I expect to pay suppliers for suppliers -- it's that simple. And for the record, I still dislike transactions and referential integrity being handled at the database level. It's handy, but it's unnecessary and rarely beneficial. It usually amounts to a limitation when everything's great, and then you want that trigger to do something complicated. And then you want that stored procedure to do something that your application does in one line of code, but requires a web-server, and your entire application, to do it.
Over the years, I've loved the simplicity of MySQL; I've loved the ease of installation; I've loved the low price -- sometimes no price; I've loved the upgrade pace. And like any good business, I stay one step behind.
I've built a successful business with MySQL as a backbone. They deserve my loyalty.
This is slashdot - I thought Python references got automatic +5 funny mods?!
People want to make money! Providing support is just not enough, you need to sell a product.
Maybe slashdot needs a bit of an overhaul eh?
Hey Man, Invading Iraq was legal too. Doesn't mean your customers/the Iraqis will thank you for it.
If you want a real database server why don't you just download oracle express? Its free to have, use and distribute however the heck you want. You can even distribute it with your commercial applications for free which I dare say can't be done with MySQL.
Its better in every concevable way than MySQL will ever be.
Then again there's also Firebird, forgot whose codebase they used.
Firebird uses Borland's Interbase.
FalconShould there be a Law?
Wonder if we'll start seeing it referred to as My$QL on /. now?
You want fun, go home and buy a monkey!
From his earlier comment:
Finally it happend. XFree died but we've got X.Org fork. Looks like this "SQL interface to the filesystem" will die as same, but maybe even with no fork. Well, I am much happier on PostgreSQL for years already.
For me, as a developer that has used MySQL for some time, this is an action that destroys trust.
They say it is to keep too many versions of MySQL from being used, a lie that is so obvious
it would have been better if they hadn't said anything at all.
This, of course, isn't the first time i have begone to wonder about the ethics of the MySQL team,
the first was when they recreated their website, hiding the 'download' section in the 'comunity' section
and even then only after making you click a 'yes i'm a total über geek, i recompile my kernel every DAY!' button.
To me that means that i can no longer trust MySQL, i can no longer trust them to not sink to even lower tactics
to get us away from using MySQL under the GPL. Now i have to fear that they not only will they withhold features as
they already do, but that they will also intentionally introduce bugs and cripple performance just so they can then state
'well, with our NON-GPL commercial Enterprise license, that wouldn't have happened'
I liked MySQL because it was quick to setup and had reliable and scalable performance, i might be able to get
similar performance etc with PostgreSQL, but it will definitely not be simple to do simple things and
it requires constant tweaking and probably the blood of sacrificially slain goat to work reliable performance wise.
Now i might even consider using the 'light' (free) version of SQL Server and Oracle, even with thier limitations,
for many projects they are enough, and for those that aren't, i now at least don't have to explain
how and why MySQL is a 'real' database engine, i can simply say,
'sure, oracle, i can do that, it will cost lot's more, but yea'
Is there hope that some one will take the source as it's now and create a new GPL branch without the
commercial BS?
The pressure on mysql to constantly offer new features, instead of focusing on mysql's strengths, which is highspeed, a decent group of features and simplicity to maintain and operate is going to cost mysql in the long run. This is only the start. The new features in mysql 5+ such as stored procedures, triggers, functions etc are very poorly implemented and come nowhere near the full implementations of databases like Oracle and Postgresql. The result is that DBAs and developers who like mysql for its easy maintenance and speed end up being disillusioned when problems start cropping up.
I don't think many places would switch to Postgresql, since the administration side is more complex and therefore more costly, but I can see shops weighing the pros and cons of switching to postgresql, since that DB has an excellent reputation.
The last thing you want to hear about a DBMS is this line from MySQL: "the company has introduced features into the Community edition of the software that "[weren't] as robust as we thought, and created some instabilities"
..."
... Oh, and look what we got here, a real company with stockshares and all to back it up! ... Btw, I happen to have this neat bargain for you right here ..."
Yepp, that's the last thing you want to hear. However this is most likely to be marketing/buy-our-enterprise-version-to-be-safe marketing FUD targeted at MySQL experienced developers who want to keep a strait face when their boss asks them about the real true stability of MySQL. "Are you really really sure it's stable? How can you guarantee it?" - "Well, we could get this new Enterprise super-safe version
MySQL AB wants to morph into a company more like Oracle or SAP, which for a decade now have not been paid bucketoads of cash for technology (that's everywhere by now) but for taking over responability. I can't really blame them, as it's the safest and fastest way to make money in the industry.
"Look, the OSS version is (at Version 5.x) suddenly starting to get a bit buggy, you better get our neat Enterprise version.
I cry FUD.
The truth is MySQL is a very mature product (as much as you can call a product that uses SQL 'mature'). It's not really been a classic RDBMS until 5.x which makes being mature a tad moot, but the people are used to using it and *are* using it for tons of products. If someone introduces hacks that cause serious trouble, people would notice right away. It's not that if Linus puts hacks into the kernel that everything comes crashing down in an instant (recent Scheduler debate anyone?). It's most likely to be the exact same with MySQL and other projects.
We suffer more in our imagination than in reality. - Seneca
Seriously, folks, Zonk is like 66% of why I no longer use my Slashdot ID. Dude takes Slashdot to Digg.com's level all by himself. Every time he posts a story, it's flamebait.
Except everything you said in your post isn't the goal of Free and open source software.
The goal isn't:
- To make a profit
- To become popular
- To attract the attention of larger companies
The goal of Free and Open Source Software is to keep the freedoms that allow you to use, modify and re-distribute. Restricting those freedoms in the name of attaining the goals you mentioned above would be completely missing the point of free and open source software, don't you think?
Now there are exceptions to this (although some hardcore GNU people will disagree). For example Ubuntu including proprietary graphics drivers so that it becomes more popular with their Goal of one day having a free and open driver to be able to switch to, when it becomes stable enough.
The things you mentioned above are nice but they should not be prioritised over the most important thing which is freedom. What MySQL has done is created a fracture in their own community between those who pay and those who don't.
I also noticed you need to use bitkeeper to download their source code, not exactly a company that embraces open source software...
While I'm not doing database stuff currently, last time I was a year or two ago, I actually saw this coming and opted for Postgres rather than MySQL.
Postgres is a fantastic project. It's very solid, can handle huge transaction/request loads, has concurrent locking etc, from memory supports a large number of different datatypes, and is also very configurable. Even better, it's under what is my own favourite license, the BSD license...so you can do pretty much whatever you want with it.
MySQL will probably continue to have its' place, with people who need the things they're charging for, (presumably support options etc) and I wish the project well.
However, for people like me who don't have a lot of money, MySQL ceased being an entirely legally safe option a while ago.
New versions of Python, and PHP, are including SQLite as part of the standard distribution. And if SQLite isn't enough, there's alwasy PostgreSQL.
Considering the MySQL AB's unusual understanding of the GPL, their goofy dual license, their non-standard implementation of SQL, and their partnership with a company that claims the GPL is illegal (scox); I really have to wonder if MySQL is the way to go anymore.
MySQL has also partnered with scox. Scox is a msft puppet. Scox has loudly claimed that the GPL is unconstitutional, and scox has written congress an open letter about it.
Scox seems a strange bedfellow for a company whose flagship product is built on the GPL.
The new versions of those languages, anyway.
Not just mediawiki. All other OSS projects should be supporting PostgreSQL !
Lets take a look and make some suggestions:
Mantis, Joomla, WebGUI, Rails (serious support: booleans), SugarCRM.
It almost seems an attempt at sadistic humor that Connector/J on Linux translates camelCase object names to CAPS, but Connector/J on Windows does not, which they've paired with respectively case-sensitive and non-case-sensitive versions of MyISAM.
GAH.
The best option for asynchronous PostgreSQL replication is Slony-I. It's extremely flexible and so far has proven to work very well. The devs supporting it are also very good. I do admit that there is a bit of a learning curve to get it configured and running, but this is something they are working on for the next major revision.
If you need to cluster PostgreSQL, have a look at pgpool and pgpool-II.
This is the usual tempest in a teapot. MySQL is in no way, as I read the article, not complying with OSS requirements. As someone elsewhere pointed out, even if MySQL doesn't distribute the tarball, any of their customers who have it can do so. So it's hardly restricting access to the tarbell. It's merely an organizational move to clearly delineate the Enterprise product from the Community product.
To illustrate the stupidity one hears in these discussions, one idiot at another OSS site said that nobody should use PostgreSQL - or even test it - because their BSD-style license allowed companies to take the code and use it and not release their proprietary enhancements. This is the sort of stupid fanaticism that gives "free" and OSS software a bad name to anyone with a brain.
These morons don't realize that some licenses were explicitly designed to allow just that - companies to develop their own products on top of OSS. This is a GOOD thing, not a bad thing. Although giving back enhancements to an OSS product to the original project is a benefit to everyone who uses that product, not EVERY enhancement is necessarily worth it and not EVERYBODY in the world needs to be a "free software" developer. It allows OSS products to find their way into more and more products, thus validating the OSS model - even if some companies do not adhere to it strictly. If the alternatives are a company using OSS and not returning improvements to the community vs not using OSS at all, obviously the latter is worse. And that is the choice companies must make.
Whether the former choice has any impact on the development of OSS is another matter entirely. The notion that somehow the entire corporate world is going to "steal" OSS and somehow convert it all to proprietary products and thus "destroy" OSS is utterly ridiculous on the face of it.
This is why Linus opposes the GPLv3 and he is correct to do so. It's the difference between a truly free market and socialism.
Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
The forums are primarily a user to user channel, not a you ask MySQL channel. Same for the IRC channel on Freenode. In both cases some employees do answer questions as an incidental part of their job. None are paid specifically to answer the questions on the forums. If it's a quiet week I might spend an hour or so doing it.
You're not paying 500 solely for access to the knowledgebase. Among other things, you're paying for the ability to ask me a question and get an answer from someone who's run MySQL on a billion plus query per day top ten site on the internet. That is: not your usual time-wasting support but someone with a clue who's used it in the real world.
MySQL doesn't own the copyright to libreadline and InnoDB. It's a reuser of those components. As such it's choosing to comply with its GPL obligations to those licensors by using clause 3a and distributing the source to just those who it gives the binaries to. Those people can than freely pass it on to others if they wish and MySQL is well aware of this.
I don't disagree with that. However, a good sign of the decline of a product is when the number of moderators and contributors willing to answer questions on public forums declines. Especially if you're locking up the knowledgebase, you're just making answers harder to find which leads to an increase in overall customer dissatisfaction and negative impressions.
Companies like Oracle, Microsoft and Google have staff who aggressively answer questions in their public forums precisely for this reason. I have no idea if they're paid to do so, but I'm sure they're encouraged to do so. If they do this voluntarily then, wow, that must say something about their attitude toward their customers.
So, tell me, what is it about MySQL AB culture which leads to people like you, who don't see it as part of their jobs to answer public user-to-user forums and expect that if people want a quality answer to a question about the product, no matter how simple, then they should pay for it.
That's the downward spiral I'm talking about...MySQL AB's inner culture and attitudes towards the end users has deteriorated and become rotten. They haven't properly struck a balance between making money off of costumers and providing good FREE support.
...are, in my limited experience, consistently sleazy.
They phoned me up within an hour of downloading the community version and tried to make me afraid of the community version. They hinted that it's less stable than the for-profit version they're selling and that I'd be much happier if I spent the money on the more reliable Enterprise version with their support package.