Today we have released MySQL Tools for Microsoft Visual Studio 1.0.2 GA --a downloadable plug-in for Visual Studio 2005 that allows Windows developers to quickly build MySQL data-driven applications with Visual Studio. With this plug-in, developers will be able to create, modify and manage MySQL database objects with an easy-to-use interface from within the Visual Studio IDE. This product is delivered as a package compatible with Visual Studio 2005 and delivers the following features:

• DDEX (Data Designer Extensibility) compatibility
• Ability to work with MySQL objects (tables, views, stored procedures, etc) from within Server Explorer
• Support for MySQL versions 4.1 and higher

IMPORTANT
This product will only work correctly with Connector/Net 5.0.2 and higher.

This release does not include the ability to work with the DataSet designer but we will be making a beta …

Solera Networks Announces Open Source License for DataEcho Web Forensics Software, Solera Networks (Press Release)

Software Freedom Law Center Files Brief with Supreme Court Arguing Against Software Patents, Software Freedom Law Center (Press Release)

Is XenSource Virtualization Ready to Go Wide?, LinuxInsider, Jay Lyman (Article)

The cloudy future of mobile Linux, Computerworld, David Haskin (Article)

Financial …

The central component of most operating systems is the kernel. The kernel manages the resources of a system. In addition, the kernel facilitates and manages the communication between a system's hardware and software components.

Two levels of execution are provided by hardware: kernel mode execution and user mode execution. When in kernel mode, the software program can access all the instructions and every accessible piece of hardware. A program is in kernel space if running in kernel mode and in user space if running in user mode.

The Solaris kernel is a monolithic kernel, much like most Unix systems, as compared to a microkernel.

The software said to be running in …

Was really surprised today when heard really funny rap song about “kill -9″ Unix command:

• Video is here.
• Lyrics is here.
• Audio record is here.

Welcome, reader, to the 23rd edition of Log Buffer, the weekly, human-edited review of the database blogosphere. No time to waste, so let’s start with some announcements. Xaprb, the producer of innotop, brings to our attention the latest release of mysqlreport, “one of (his) favorite tools for quickly comprehending the overall state of a [...]

Here's a mystery festive stored procedure. Don't run it on any critical servers.

MySQL's user variables have interesting properties that enable the useful techniques I wrote about in recent articles. One property is that you can read from and assign to a user variable simultaneously, because an assignment can be an r-value (the result of the assignment is the final value of the variable). Another property, which sometimes causes confusing behavior, is un-intuitive evaluation time. In this post I'll show you how to make sure your variables get updated at the time they're used, instead of potentially reading and updating them at different stages of query execution. This technique enables a whole new range of applications for user variables. As a bonus, it also avoids extra columns of output created by variable manipulations.

Just a quick note to let you know that I’ve written a new technical in-depth white paper on the MySQL 5.1 server that you can now download from our site. It covers all the new features in 5.1 and provides some technical examples of each enhancement that our new release offers. Check it out when you get a chance and let me know if you have any questions.

I have just committed the initial implementation of foreign keys for the PrimeBase XT storage engine, whew! The implementation is similar to that of InnoDB and supports the RESTRICT, CASCADE and SET NULL options.

Currently the PBXT implementation requires that the data types of the referenced columns are identical. InnoDB allows references between CHAR and VARCHAR and strings of different length. PBXT also requires that the index used by foreign keys have the exact number of components. InnoDB can use indexes that have more components than the number of columns specified in the foreign key declaration.

On the other hand, PBXT supports all SQL syntax that can be used to create foreign keys. This includes the following syntax which is not supported by InnoDB:

CREATE TABLE t2 (
id INT PRIMARY KEY,
fk int REFERENCES t1(id)
) ENGINE=pbxt;

Maybe you are wondering why one …

This bug 15815 a huge problem in thread handling with INNODB-will not be available for the Community Edition. Here are your options:

1. 
   
2. Upgrade to 5.0
   
3. Get a support contract that enables the Enterprise Edition
   
4. Hope that pressure from the community will push MySQL to giving this patch to the masses
   

What sort of compensation would MySQL need to allow this patch into the community edition?

Getting everyone to use 5.0 is good for MySQL, maintaining what 5 versions of mySQL must suck. Also to keep this product alive, it takes money and talented engineers that need money too! Yet, for me personally I like 4.1 so I want to be a bit selfish and get this into the 4.1 community edition :)