MySQL Editions
mysql.com
mysql.com
I also wonder how these pricing changes impact the already hurting community of open source developers supporting the community version.
If you're worried about the future, Oracle agreed to maintain the dual-licensing strategy until at least 2015 as part of the EU negotiations before acquiring Sun.
The FSF call it "mere aggregation": http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
I don't know whether SUN and Oracle still pursue that strategy. Otherwise you could indeed bundle MySQL with some clean-room libraries to talk to the server.
That doesn't sound legal. You're allowed to clean-room implement anything aren't you?
That does indeed sound crazy, but they also had piles of cash to throw at lawyers to go after anyone who challenged them, and (maybe as a result of that) nobody ever made e.g. a clean-room BSD or LGPL licensed version of the mysql library. So it never made it to court AFAIK.
The reality is that copyright covers verbatim copying. If you read a book and write a review, the term "derived work" makes English sense, but not legal sense. Similarly, if you read the MySQL code looking for magic words to say to the server to get it to give you data, saying those words is not copyright infringement. It's "learning", not "copying".
If anyone used MySQL, I would write a BSD-licensed API just to prove a point. (And to be non-blocking.) But the world has moved on since the Oracle deal...
What would happen, if the protocol would require sending a picture of a picture of Mickey Mouse with each request (or some copy-righted novel)?
In fact if you spend much time thinking about this it isn't at all hard to come up with a lot of scenarios that law doesn't have an answer for, in theory or in practice.
In short, it's fair use.
I believe MySQL/Sun used to make a lot of money dual licensing the GPL client library. No longer!
It doesn't. The acceptance of the GPL (as of V2, haven't read V3) for a software component does not compel you to use any particular license for your own work. You can, by distributing the GPL'd work with you own non-open software, be in violation of the license on the GPL'd work, but the repercussion is a loss of the right to distribute the GPL'd work potentially enforced by injunction, and not an automatic change of your own license as the phrase "make your application GPL as well" implies.
If you are redistributing it (you ship it to your customers and they deploy it on their servers) I would find a lawyer.
It's clear that someone doing proprietary software on top of mysql have to get proprietary-compatible license for mysql.
But. How this happens, that community submitted code/patches/etc gives Oracle profits? Isn't including any patch/code from GPL version into Proprietary version automatically enforce GPL rules and makes impossible to include this software into any other proprietary software?
I saw this with other projects too. I am really interested how company behind product can provide both proprietary and gpl licenses for their products.
So clearly they can not be selling software, I can only assume these are prices for support, not for software.
Have they taken down download links? Removed source code?
Edit: I guess I can see how you can read it in reverse from what I meant.
"Selling software" is distinct from "preventing others from selling copies of [said] software", and confusing the two is the source of much fear, uncertainty, and doubt about the GPL, so some people get a little defensive when they're conflated. When I ran a small software shop, most of the work I sold to small business was built on libraries and other works that were GPL, but this didn't prevent me from charging money for it, it just meant that I couldn't prevent them from selling or giving away copies themselves. Of course, few small businesses are interested in paying for software and then providing it to their competitors, so in practice that never mattered.
Embedded Database6
6 MySQL Classic Edition is not available as an Annual Subscription. ISVs, OEMs and VARs can purchase a license to use as an embedded database.
Business first, not the heart and minds of developers.
Luckily the 'L' + 'A' + 'P' cannot be bought.
LAPP stack anyone?
Unless P=Python? :-)
LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".
Am I normal?
For example: http://tagwalk.com/tag/MySQL
I hope your development is driven by accurate profiling and benchmarks. It's much better to have a dirty, but very surgical fix in a specific bottle-neck, than to have your application "scaled" with too many layers of individually "optimized" components, that bog each other to a crawl when combined.
Mono for long-running and complex backend processes.
nginx, PHP, MySQL, memcache - for presentation - quick!
node.js provides an event bus between PHP and Mono
MongoDB is taking over from storing large blobs of JSON in MySQL.
I was on the opposite side of things, when I did we last. I had language integrated into the web server, and I wrote my own caching primitives. All optimization went into the request handler, and optimizing a single function is easier than debugging a whole stack.
A decent solution, but it had no massive inputs, so I slept better at night knowing it wasn't being tested.
rails, sinatra, mysql, resque, custom email server (looking for a name...), memcached.
How the heck do you mix in mono?!?
[edit] I mis-clicked and upvoted you when I meant to downvote. Incendiary statements about valuable technology has no purpose here.
So, back in the day, that drove me to conclude that all the MySQL fans were crazy, and I decided to use Postgres at home, since Windows != server, and having done quite enough XBase once upon a time, DB integrity had some value to me.
LAPP? Bring it!
Is the final P PHP, or Perl (which would be my preference)? Maybe make it an R for Ruby? :-)
I bet the whole community will support the new sql.
I don't see anyone rushing to abandon mainline MySQL for the forks.
If you're not familiar with Drizzle, it's MySQL that has a bunch of crap you'll never use stripped out.
Can't really grasp that. Drizzle is MySQL minus cruft... Its parts have been extensively tested for many years.
A pretty basic feature I thought, which is included in the free version of PostgreSQL.
mysqldump --single-transaction
This option sends a START TRANSACTION SQL statement to the server before dumping data. It is useful only with transactional tables such as InnoDB, because then it dumps the consistent state of the database at the time when BEGIN was issued without blocking any applications.
Time to start boning back up of Postgres, I guess.
Edit “Classic Edition” — what a cop-out name. It should be “Crippled edition.”
The "N/A" price probably just means "contact us so our sales team can squeeze you for all you're worth" -- which is how enterprise software deals typically work.