Last week professor Eben Moglen published an SFLC position paper related to the EU investigation on the Oracle Sun merger. Even though most of the proceedings do not happen in public, the SFLC publishing its own paper allowed us to answer it to the Commission. While it is not our primary objective - and we are a bit constrained at this point - to educate the public or debate this. But given that it is something everyone likes to have an opinion on, and the SFLC has already opened the discussion, we have decided to also publish our submission as well.

We would like to emphasize the following paragraph from the introduction.

read more

Devart today previewed dbForge Studio for MySQL 4.00, scheduled for release this December, and announced the immediate availability of a beta release that supplies database-dealing people with the very data management capabilities they want.

Having accumulated extensive knowledge in data management preferences and routines, Devart has created dbForge Studio for MySQL 4.00 Beta that predicts and delivers expected capabilities in any phase of dealing with data. The users can manage the data from soup to nuts in one place and with the same little effort as usual.

The highlights of dbForge Studio for MySQL 4.00 Beta include:

• Data Import. Guided by a click-and-pick wizard, the users can easily import data from seven widely-popular formats (CSV, DBF, MS Access, MS Excel, ODBC, Text, XML) with a multitude of settings to …

ClusterJ Architecture

MySQL have been working on a new way of accessing MySQL Cluster using Java. The aim being to give most of the performance of the C++ NDB API but in a much friendlier form for Java developers. There will in fact be 2 new interfaces – ClusterJ (MySQL’s own API) and a JPA solution (using OpenJPA). If you want to see for yourself then take a look at the Blog entry from Bernhard Ocklin – the engineering manager responsible for this work.

Most of this year I have been working on the MariaDB project. So it is interesting to look back and see what has been achieved.

For those that do not know, MariaDB is a project to create a community-oriented branch of the MySQL code base. We want MariaDB to be developed for the community, by the community, and driven by the needs of the community.

Turns out that a lot has been achieved already:

• We have had three releases (and a fourth is being prepared currently). The code is getting close now to release candidate.
• We have apt-able (and yum-able on Centos/RHEL) repositories for the releases. These are based on the OurDelta infrastructure (scripts, build machines, etc). This means MariaDB installation and upgrade can be done the prefered way using the built-in package …

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

One of the many cool new features in Java EE 6, is support for the DataSourceDefinition annotation.

The DataSourceDefinition annotation provides a way to define a DataSource and register it with JNDI. The annotation provided annotation elements for the commonly used DataSource properties. Additional standard and vendor specific properties may also be specified.

So let us look at an example:

@DataSourceDefinition(name = "java:global/MyApp/myDS",

className = "org.apache.derby.jdbc.ClientDataSource",

portNumber = 1527,

serverName = "localhost",

databaseName = "testDB",

user = "lance",

password = "secret",

properties = {"createDatabase=create"}) )

The data source will be registered using the value specified in the name element and can be defined in any valid Java EE name space and that will determine the accessibility of the data …

One of the many cool new features in Java EE 6, is support for the DataSourceDefinition annotation.

The DataSourceDefinition annotation provides a way to define a DataSource and register it with JNDI. The annotation provided annotation elements for the commonly used DataSource properties. Additional standard and vendor specific properties may also be specified.

So let us look at an example:

@DataSourceDefinition(name = "java:global/MyApp/myDS",
className = "org.apache.derby.jdbc.ClientDataSource",
portNumber = 1527,
serverName = "localhost",
databaseName = "testDB",
user = "lance",
password = "secret",
properties = {"createDatabase=create"}) )

The data source will be registered using the value specified in the name element and can be defined in any valid Java EE name space and that will determine the accessibility of the data source from other …

One of the many cool new features in Java EE 6, is support for the DataSourceDefinition annotation.

The DataSourceDefinition annotation provides a way to define a DataSource and register it with JNDI. The annotation provided annotation elements for the commonly used DataSource properties. Additional standard and vendor specific properties may also be specified.

So let us look at an example:

@DataSourceDefinition(name = "java:global/MyApp/myDS",

className = "org.apache.derby.jdbc.ClientDataSource",

portNumber = 1527,

serverName = "localhost",

databaseName = "testDB",

user = "lance",

password = "secret",

properties = {"createDatabase=create"}) )

The data source will be registered using the value specified in the name element and can be defined in any valid Java EE name space and that will determine the accessibility of the data …

O’Reilly’s official website announces that they are planning a MySQL conference in 2010 (same time, same place). Unlike past years, it isn’t co-presented with Sun/MySQL; they are flying solo. The theme is Information Unleashed.