In Linux, MySQL on August 23, 2012 at 1:18 pm
Recent Oracle behaviour on MySQL releases have baffled quite a number of MySQL followers. According to this:
a recent version: mysql-5.5.25, does not have the usual regression testing scripts available. These scripts have been part and parcel of MySQL since 1999 and not having these for the first time is a real surprise for active MySQL developers.
So how important are these scripts? well it turns out they are very important as it contains a compilation of old and new scripts that verify the new MySQL version a) does not have the old bugs identified with previous versions and b) contains the fixes for newer bugs.
In other words, a missing regression testing script means, the quality of this version is suspect. Probably just what the powers that be in Oracle wants to happen. As of this writing Oracle has already released 5.5.27, I wonder if that and .26 also have those scripts missing.
More than two years ago, I wrote about how Oracle only “committed” to a parallel release of the free version of MySQL up to 5 years from the closing of the purchase (of Sun and its bag of goodies) transaction. After that it’s anybody’s guess. Five years hence is January 28, 2015. Two and a half years to go, but before then I suspect we’ll see more reasons to ‘doubt’ the open future of MySQL.
In Database, FlexOODB, Java, Linux, MySQL on October 30, 2011 at 8:40 am
Aside from Netbeans, an SSH client and a good text editor, a good database manager always comes in handy when developing apps.
I’ve been using HeidiSQL previously to manage my MySQL databases when my laptop was on XP, in its current incarnation as a Fedora 15 development machine, I’ve been hard pressed looking for an alternative, HeidiSQL on Wine is simply unusable. I had to content myself with MySQL’s WorkBench Tool. WorkBench is free but I find the interface clunky.
Then I ran into DBeaver, its a Java app that has the familiar interface of HeidiSQL with the added difference that it works across platforms (of course). Plus, unlike HeidiSQL which can only connect to MySQL (although I understand there’s work in making it work for MS SQL too), DBeaver can also connect to other popular RDBMS: Oracle, Cache, DB2, Firebird, Derby, H2, HSQLDB, MS SQL, Postgres, Sybase, SQLite etc.
Here’s a screenshot:
Here’s a quick how to to install in your Linux box:
- Download DBeaver and extract in your drive (e.g. /home/<username>)
- Right-Click on an empty spot on your desktop and select ‘Create Launcher’
- Type in ‘DBeaver’ (or any name for that matter) click on ‘Browse’ and go to the /home/<username>/dbeaver directory and double click on the dbeaver file.
- To replace the default icon, you can click on the icon link of the create launcher window and select the file /home/<username>/dbeaver/icon.xpm. That’s it.
Thanks for a great tool DBeaver Team! =)
In Database, Linux, MySQL on September 19, 2011 at 8:57 am
In early 2010, I noted that Oracle will only guarantee support to the open source version of MySQL until the end of January 2015 (or 5 years after the end of the transaction — that being the purchase of MySQL). A year and a half on and it looks like its well on schedule recently announcing that they’re now offering ‘commercial extensions‘ to the product.
The implication for this is obvious: we’re going to see more of these feature sets and ‘improvements’ on the commercial version of MySQL as opposed to the community version as to create enough doubt for corporate users who are a class of their own and who would invariably go for a more expensive solution ‘just to make sure’. The end result? why use open source mysql when you can buy? the purchase was, afterall, sweet revenge, as Oracle is able to effectively throttle competition from left field.
Purchasing MySQL is a medium term insurance policy, one which will have a maturity date of January 28, 2015.