Poo-tee-weet

Re: Oracle needs to get hurt .. badly!

Lukas Kahwe Smith — Mon, 16 Aug 2010 17:46:33 +0200

Yes, I am hoping that only a single well concerted statement would be necessary. To give it more weight I think it shouldn't just be words though, which is what brought me to the idea of dropping Oracle product support from the next release.

I should clarify a two things here:

With next release, I mean only the next release and not necessarily releases after the next release
Especially in regards to MySQL, I am aware that several non Oracle products (aka MySQL forks) speak the same protocol and for obvious reasons therefore do not have separate drivers in most products. Just stripping MySQL support would kick out all these non Oracle products. It would make sense to rename the drivers, because then which name do you choose (MariaDB, OpenQuery, Percona etc)? And just duplicate them to give each their own also doesn't make technical sense. Furthermore in the end MySQL users could still connect. So I am not sure if it would make sense to strip MySQL support.

Re: Oracle needs to get hurt .. badly!

Chuck Burgess — Mon, 16 Aug 2010 16:37:55 +0200

Perhaps the key here is not a sustained boycott type of effort targeting their bottom line... perhaps a successful "statement" of many projects near-simultaneously releasing Oracle-less versions would garner enough _news_ to make the _statement_ itself significant.

A resignation of a key official due to a policy disagreement isn't designed to make a pragmatic difference in and of itself... it's designed to be a statement that gets heard and makes others think. Maybe the wording around an Oracle-gutting from a software release could use the term "resign", e.g. "we are _resigning_ our Oracle interoperability in response to their patent litigation".

Re: Deploying app updates to a cluster

Gonzalo Ayuso — Mon, 16 Aug 2010 15:42:48 +0200

@Tyrael
Im my case normally it isn't a problem if nodes upgrade at different time. Hg push/pull commands are fast enough, but if I really want to ensure the atomisation of the change I always can stop the webserver in the nodes and start it again when the change is done (if I can assume it of course)

Re: Oracle needs to get hurt .. badly!

Paul — Mon, 16 Aug 2010 15:17:36 +0200

Don't forget about Drizzle as a MySQL alternative as well. Although it was started by a bunch of guys that were all on Sun's payroll I think they left when the merger happpened.

I've been thinking, as someone who is forced to deal with Oracle's ERP software, you could write a pretty good ERP system for smal to medium businesses using PHP.

Take a look here

Tore — Mon, 16 Aug 2010 14:18:13 +0200

Maybe starting using software from these guys is a good start...

http://www.percona.com/software/

http://www.mysqlperformanceblog.com/

These guys seem to be pretty serious about what they do.