Resulting from one and a half year of busy development, HeidiSQL v4.0 is now ready.

Here are some of the new features:
* Completely rewritten user manager
* New grid and popup editors for text, blobs, date/time, set, and enum
* New editor for VIEWs
* New editor for stored procedures and functions
* Customizable colors for grid cells, according to data type
* Direct SQL export from grids
* …

Last week at the MySQL Conference & Expo I made a release right before my first Gearman talk. I didn’t get a chance to blog about it, so here it is now. This is a fairly big release since it includes a major refactoring of the job server to now be threaded. Doing some simple tests on it with a 16-core Intel machine:

The Y axis is total jobs/second, and the X axis is number of clients/workers (8×8 means 8 clients and 8 workers). The clients and workers are the ‘blobslap’ utilities included in the source, and they are shoving as many jobs/second through the server as they can. Job size was random between 0 and 1024 bytes. The job server peaked out at about 43,000 jobs/second, most likely due to the machine being so busy (running job server, workers, and clients). The job server uses all non-blocking I/O with a …

MySQL 5.4 comes with Innodb engine which seems to have much better performance than MySQL 5.0 - this is due to locking and IO patches from Google integrated in this release (which are similar to appropriate Percona patches) as well as some unique fixes such as different innodb_thread_concurrency handling and other optimization.

Should we take Innodb from MySQL 5.4 and merry it with unique Percona patches (adaptive checkpoints, additional undo slots, profiling, etc) and integrate it with MySQL 5.0 ? How useful would you find it ?

Currently we see a lot of customers not quite ready to update to MySQL 5.1 in particular as there is little in this version which benefits their workload, which consists of the queries running just fine on 5.0.
5.4 especially introduces optimizer changes which besides positive impact for some queries may …

This year the fabulous OSDC conference is 25-27 November 2009 and returning to Brisbane (Bardon Centre, Mt.Cootha which is a great venue tucked into a rainforest setting). Stephen Thorne leads the organisation team for this event.

The call for papers is now open, until June 30th. For full details, see OSDC 2009 call for papers.

We’ll definitely be there, particularly since it’s very close to Arjen’s house. And perhaps we’ll get some talks accepted on MySQL and other topics. We’ll definitely be submitting some proposals!

Fixed a lingering JS issue with the ExtJS code in header.php file that was preventing IE7 from loading the main.php page. It was….. an extra comma! If you are inclined to edit one file here is the diff change, otherwise like other bug fixes it will be included with the next release. The file is system/application/views/header.php and the change is for line #327 for revision 42+.

< {id: 'innodb_total', header: "innodb_total", width: 75, sortable: true, renderer: 'fileSize', dataIndex: 'innodb_total'},
---
> {id: 'innodb_total', header: "innodb_total", width: 75, sortable: true, renderer: 'fileSize', dataIndex: 'innodb_total'}


MySQL provides a SOUNDEX() function, which returns the soundex of a given string. For details, refer to the manual, but to put it simply, it allows you to compare strings based on how they sound, hence letting you do proximity searches on your database. If you’re just querying for a word, it’s usage is pretty […]

Related posts:

1. Extending procedure_analyse My previous post explored a stored procedure that extended procedure_analyse...
2. Making use of procedure analyse() SELECT Field0[,Field1,Field2,…] FROM TABLE PROCEDURE ANALYSE() is a nice tool...

YARPP powered by AdBistroPowered by

As you may or may not know, long long ago (in this universe) I used to be the MySQL documentation team  Yes, a team of one. This was 2001. It was a great and interesting time. The current much extended team is doing a great job with the now much bigger set of docs!

Today, I find myself disagreeing with my former colleagues on one particular aspect, namely its licensing. You see, the documentation has never been released under an open license, it used to be plainly copyright all rights reserved, and later some rights were granted to distribute the docs together with the server.

Statements made earlier by Karen Padir regarding possible opening up of the docs license filled us with hope. Then, Stefan Hinz (the current docs team lead) wrote a blog entry MySQL documentation: no license change. Some of the arguments there we can …

Opentaps Now Supports Hibernate
We made a very significant and fundamental enhancements: opentaps now supports hibernate as well as the original ofbiz entity engine. You can use the two interchangeably to store and retrieve data, but the addition of hibernate also gives us a more flexible query language, data validation, search, and distributed database capabilities. We think this will open up a lot of new opportunities for opentaps down the road.
Asterisk VOIP PBX Also Integrated
Another important enhancement is the integration of opentaps with the asterisk open source voice over IP (VOIP) PBX. You can now use it with opentaps CRM, purchasing, and other applications for inbound and outbound calls.
Enhanced Manufacturing and Inventory Planning
…

By now many folks know that MySQL documentation is not changing its license. This is an issue with many sides, but before I go through them, I want to address a comment made by Masood Mortazavi:

People who are interested in forking the server — and potentially interested in creating what is in effect separate communities of their own — should probably develop their own docs for their own forks.

(There is a cost involved here, I know. However, it should be a cost worth paying if developers of forks really believe in their work. MySQL AB certainly paid that cost in developing the docs while it had already made the code itself freely available under GPL. So, the playing ground among all forks, etc., …

If you run IE7 and have tried Kontrollbase you may have noticed an infinite progress bar for the authentication. While login works on all other browsers, it was broken on IE7. The change has been committed to the repo and will be available in the next release. If you are inclined to edit one file here is the diff change. The file is system/application/controllers/login.php and the change is for line #68.

68c68
< $user_system_user_id = $this->session->userdata('user_system_user_id');
---
> $user_system_user_id = $this->phpsession->get('user_system_user_id');