I'm pleased to announce the release of Spider storage engine version 2.7(beta).
Spider is a Storage Engine for database sharding.
http://spiderformysql.com/

The main changes in this version are following.
- Spider table can load balance using multiple links at searching without locking. Load balance rule is "((server_id + thread_id) % number_of_links)".
  Please write multiple connection informations splitting space characters at "host", "user", "table", "server", "socket", "wrapper", "database" and "password" table parameters.
  Example: "host 'h1 h2 h3'"

I will continue to develop Spider's functions for Active-Active type clustering.

Please see "99_change_logs.txt" in the download documents for checking other changes.

Enjoy!

One of the elements that I have wanted to add to the installation chapter for some time has been some flowcharts to make understanding the steps required to successfully complete an installation on various platforms.

The Windows one is the most interesting, because not only do we have the installer, but we also have the MySQL Server Instance Config Wizard which has its own sequence of steps to configure an instance of the server.

I’m still working out and refining the examples and the graphics, but here is an example of the config wizard output:

Hopefully the full suite of images will be in the documentation shortly – all comments and input welcome.

I’m finding myself smiling today. I lay in bed last night thinking about a number of milestones that this month marks for me.

October 15th marked four months since the last time I had a cigarette. I feel good about my chances at remaining smoke-free for the remainder of my life.

October 18th marked one year since I officially began working on the Drizzle project. Although, as Giuseppe can attest to, I had been contributing to Drizzle before October 18th, 2008, that date was the official start.

I think about how much has been accomplished by the Drizzle community since that time. The Drizzle of October 2008 is barely recognizable now. Monty’s incredible work on the build system, …

In December, I'll give a talk at SAPO Codebits 2009 in Lisbon, Portual. SAPO Codebits is a hacking event held in Portugal annually, completely organized and sponsored by SAPO, a portuguese ISP and subsidiary company of the Portugal Telecom Group.

I will be speaking about web server architectures, web services in general and discuss the pros and cons of different programing languages (like PHP, Java, Python, Ruby, Perl, JavaScript, ASP.NET) and database technologies in the field of web application development, deployment and hosting. In order to save time and keep development costs at a reasonable level, it's very important to identify system flaws and architectural weaknesses in an early stage of the development process.

The talk shows pitfalls and common mistakes developers make when building …

What will you do if one day some one ask you to find single string in all databases, all tables and in all columns, In MySQL Database? This article presents a practical solution…

The post how to search / find through all databases, tables, columns in MySQL first appeared on Change Is Inevitable.

A few weeks ago I proposed a project to students at Portland State University for their senior capstone class, and this weekend I found out it was chosen by a group! The project will be a rewrite of the command line tool (the Drizzle tool is currently based on the ‘mysql’ tool), plus a lot of new features. We’re really excited to be working with them, and they seem equally excited about the project too. I hope DBAs, developers, and other folks in the Drizzle/MySQL/MariaDB communities will work with them to help define what features should be part of this new command line client. Some new features we have in mind are background queries, piping and redirection of queries (like a normal shell), and plugin support. It will also support at least the MySQL/MariaDB protocol too since it will be built on libdrizzle, but possibly more if we end up using a common DB API (we’re pondering Python). If you …

HeidiSQL now uses a more lightweight database layer to access MySQL servers. This completely new written layer consists of just two units and replaces the big ZeosDBO package - which worked well over the years, but I felt that here and there developping new features regarding the libmysql API was a pain.

Unfortunately there is nothing to show you here, no screenshot available, but in fact that was one of the most critical change over the last year.

* The UPX compressed executable's size has decreased from 1,1M to 900K.
* Should also result in better performance in some cases.

As an alternative to another recent blog post that answered the question “how can I truncate all the tables in my database,” I thought I’d show another way to do it, which does not use the INFORMATION_SCHEMA. $ wget http://www.maatkit.org/get/mk-find $ perl mk-find --exec 'TRUNCATE TABLE %D.%N' The other example is how to alter MyISAM tables to be InnoDB. That one’s easy, too. Let’s alter all MyISAM tables in the ‘test’ database:

SilverStripe is a open source content management system(CMS) to create and
maintain website, it is currently published to the OpenSolaris /contib repository.

Installation of SilverStripe on OpenSolaris is straightforward by simply clicking
the installation button on the silverstrip's 'install.php' page,
however, the installation didn't work complaining with mysql query
execution failed:

"[User Error]  Couldn't run query: SELECT `SiteTree_Live`.*,
`GhostPage_Live`.*, `ErrorPage_Live`.*, `RedirectorPage_Live`.*,
`VirtualPage_Live`.*, `SiteTree_Live`.ID,
if(`SiteTree_Live`.ClassName,`SiteTree_Live`.ClassName,'SiteTree') AS
RecordClassName FROM `SiteTree_Live` LEFT JOIN …

As pointed out by Schlomi Noach on my last blog, MySAR was already taken by a project related to Squid reports with MySQL. I decided then to look for a new name, and as I posted initially, I want to keep the sar prefix to describe the script’s purpose by association with the OS utility of the same name. I brainstormed many names. I liked Dave Edwards’s suggestion: SARkila, but it sounds too close to tequila, so I settled with Sheeri Cabral’s suggestion: sar-sql.

The title of the Launchpad page already reflects the change. What remains to be done is: a) change the name of the Perl script and documentation; and b) change the Launchpad URL. It is likely that I will change the name of the script when I release version 1.x (see below). I’m not sure of all the implications in Bazaar …