For anyone wondering, how the “Dual Licensing” business model of MySQL works, they have briefly explained it in a news posting:

As second-generation open source vendors, MySQL AB, Sleepycat Software and Trolltech AS make the majority of their revenue from selling software licenses. This license-based business model offers higher margins than services-based businesses. Historically, most open source companies have tried to make money by selling services and support.

The guiding principle behind dual licensing is “quid pro quo,” or a fair exchange. Under this model, vendors offer their products under both an open source license and a commercial license. This allows open source projects to use the software at no cost, which contributes to widespread use and testing of the software and the fast growth of a large installed user base. Companies redistributing the software as part of commercial products can also get the benefits of the open source software by purchasing a commercial license, which releases them from requirements to publish their source code. Commercially-licensed customers generate revenue for the open source vendors, which contributes to the rapid development of high-quality software.

I thought about the term “fair exchange” and came to the conclusion that the Dual Licensing business model is based on three crucial factors: knowledge, time, money.

This means: If you’re a FOSS software developer, you might have a basic understanding of which licenses are compatible and which are not. If you’re a software developer in a company that has never dealt with FOSS licensing issues but would like to use MySQL for example, you could either consult one or more lawyers that analyse the situation for you. The other option would be to pay the costs for a commercial MySQL license, which are marginal compared to what the lawyers would charge.

Seen from that perspective, the Dual Licensing model is fair in terms of how much the software user knows about the topic: If you do not have money, but time to investigate and inform yourself about FOSS licensing and you produce FOSS software yourself, you can do your work without any financial burdon. On the other hand, if you have money and you’re short on time analysing the whole issue, simply pay the fee for a commercial license.

The revenue of companies like MySQL is based on the three crucial factors “knowledge”, “time”, “money”. Dual Licensing shows that software companies who in fact produce true knowledge goods, can make money based on these factors and behave fair as well as profitable in a knowledge economy. It is also important to understand that there are two kinds of revenue they make: financial revenue from commercial licenses and revenue in terms of knowledge and lower development costs. The later is what MySQL gets back from a FOSS community that might not buy commercial licenses, but do testing, bug fixing, APIs, etc.

In a knowledge economy, “knowledge” is a good that gains value the more you have of it - other then the industrial economy, where goods usually loose value if the market is saturated. The Dual Licensing business model somehow plays industrial if you want to combine FOSS software with non-FOSS software, i.e. if you do not adhere to the standards of a community of open knowledge transfer. Then you will have to pay for the software aka knowledge good, just as if it were a car. On the other hand, if you are part of the open knowledge transfer aka a free community (”free” as in “freedom of speach”), you can use for example a GPLed software for free (”free” like in “free lunch”).

Zak Greant and Georg Richter have put together an excellent article on the new MySQL extension.

The current issue of the German Linux-Magazin ships with a review I wrote about MySQL-Administrator.

MySQL just released a development version of MySQL Administrator. I tested it for the German LinuxMagazin last week. The article will be published in the forthcoming issue. In sum: try out the administrator, it’s definitely worth it, even if you’re a shell fetishist

Yep, finally, its there: snaps.mysql.com.

Zak and Georg held a presentation on the new PHP MySQL extension (mysqli) in Hamburg. I’ve attended this presentation where they summarized all the infos about the latest development. Their slides are available online - a must-read for all PHP developers with lots of useful tips!

Today, the current issue of iX has published my article on transactions in MySQL. It’s a comprehensive and brief introduction to the topic. The text is written in German. To obtain it, you buy iX at a kiosk or in a fiew weeks online in the virtual kiosk.

Just attended Kaj Arnö’s talk MySQL, SAP and the Enterprise. Kay explained the development process of merging SAP DB and MySQL. For the mediate future, a proxy will be integrated in the SAP DB client, which allows MySQL users to manage SAP DB via the MySQL clients like mysql, mysqldump, mysqlimport. In the long run, functionality will be added to MySQL that covers the functionality already provided by SAP DB (e.g. stored procedures, triggers, standardized error behaviour, …). At the end of this process, the “MySQL Enterprise” edition (this is not the official, but the working name) will incorporate the best from both worlds: MySQL robustness, ease of use, and SAP DB enterprise functionality.

It’s also good news that all the nice DB management GUIs available for SAP DB will then also work with MySQL.

UPDATE: MySQL has branded SAP DB MaxDB

The latest release MySQL 4.0.14 introduced a neat new feature:

[snip]
Enabled `INSERT' from `SELECT' when the table into which the records are inserted is also a table listed in the `SELECT'.
[/snip]

This means you can now issue a statement like

INSERT INTO table ( field ) SELECT field FROM table WHERE field = "data";

which copies all records meeting the specified criteria to the same table.

The MySQL manual only states the behaviour previous to 4.0.14:

[snip]
The target table of the INSERT statement cannot appear in the FROM clause of the SELECT part of the query. (The problem is that the SELECT possibly would find records that were inserted earlier during the same run. When using subquery clauses, the situation could easily be very confusing.)
[/snip]

The code and data for demonstrating MySQL 4.1's new OpenGIS (geographic data) functionality is now available for download [1]. This demo has been demonstrated by Bar at the MySQL Users Conference [2].

[1] gd.tar.gz
[2] GIS session