The latest from the MySQL community

JasperSoft’s business development director Andrew Lampitt has kicked off his new blog with an interesting post related to business models used by open source-related vendors.

In it he attempts to define the approach utilized by the likes of JasperSoft and SugarCRM, which offer open source products with core functionality, as well as commercial extensions. The approach is a twist on the dual licensing approach made famous by MySQL* where the vendor, as copyright holder, makes the code available under both the GNU GPL and a commercial license for customers that would rather avoid the GPL.

The approach taken by JasperSoft et al is not to segment by user base but by features. As Andrew explains, “the commercial license is a super-set of the open source product, i.e., it offers premium product features that you will not see in …

Q4M (Queue for MySQL) Version 0.8.3 has been released with following Changes.

• fix race condition error that might lead to deadlock on shutdown
• support for FreeBSD

With support for FreeBSD added, prebuilt binaries are provided for the platforms below.

• linux (i386)
• linux (x86_64)
• freebsd-6 (i386) (should work on FreeBSD 7 as well with compat6x package installed)
• Mac OS X 10.4 (x86)

I'm back home from DrupalCon 2008 now - it has been a great event! I met a lot of nice people from the Drupal Community and learned a lot about this CMS. I've been very busy in uploading the remaining pictures from the event to my gallery - so here's for your viewing pleasure:

• Impressions from Szeged
• Day One - 2008-08-27
• Day Two - 2008-08-28
• …

Event Schedulers are "temporal" triggers.

More at http://dev.mysql.com/doc/refman/5.1/en/events-overview.html

Event Schedulers are "temporal" triggers.

More at http://dev.mysql.com/doc/refman/5.1/en/events-overview.html

One way to look at a database is that

1. 
   
2. there is data, and
   
3. there are ways to access data.
   

This dichotomy was actually coined (whether intentional or not) by Vinay in the MySQL telecom team when discussing the MySQL Cluster vision some months ago.

Even if you typically think of MySQL Cluster as just a clustered version of the plain old MySQL server, it is actually more like the opposite is true, if you consider the architecture and history of MySQL Cluster. The original cluster was just the data store called Network DataBase or NDB as we familiarly know it still. Then MySQL Server was integrated on top of that to provide an SQL interface. The original and "native" NDB interface is still there though, and many prefer to use direct C++ or Java access to their …

This week I've worked with the customer doing certain work during maintenance window which involved a lot of data copying around between MySQL boxes. We had prepared well and had measured how fast we could copy the data between servers of these kind connected to the same network, and we did the same thing before. Using simple tar+netcat based copy we can get 80-90MB/sec on 1GigE assuming RAID is powerful enough. This applies to large Innodb tables with not overly fragmented tablespace, or it is easy to become IO bound rather than network bound.

As I mentioned you can get even better with using fast parallel compression like LZO or QuickLZ but there was no need in this case.

So estimates were great but once we had started the real copy process we saw the copy speed about …

One way to look at a database is that

1. 
   
2. there is data, and
   
3. there are ways to access data.
   

This dichotomy was actually coined (whether intentional or not) by Vinay in the MySQL telecom team when discussing the MySQL Cluster vision some months ago.

Even if you typically think of MySQL Cluster as just a clustered version of the plain old MySQL server, it is actually more like the opposite is true, if you consider the architecture and history of MySQL Cluster. The original cluster was just the data store called Network DataBase or NDB as we familiarly know it still. Then MySQL Server was integrated on top of that to provide an SQL interface. The original and "native" NDB interface is still there though, and many prefer to use direct C++ or Java access to their …

One way to look at a database is that

1. 
   
2. there is data, and
   
3. there are ways to access data.
   

This dichotomy was actually coined (whether intentional or not) by Vinay in the MySQL telecom team when discussing the MySQL Cluster vision some months ago.

Even if you typically think of MySQL Cluster as just a clustered version of the plain old MySQL server, it is actually more like the opposite is true, if you consider the architecture and history of MySQL Cluster. The original cluster was just the data store called Network DataBase or NDB as we familiarly know it still. Then MySQL Server was integrated on top of that to provide an SQL interface. The original and "native" NDB interface is still there though, and many prefer to use direct C++ or Java access to their …