A couple of months ago my Asterisk box bit the dust. What happened? As far as I can tell the motherboard gave up the ghost. Which is a new event for me, I've never had a motherboard die before!

So what does this mean?

It meant finding a box to put my Digium cards in. I tried the cheap- ass route of reusing another old computer in the house, only to discover that it too had problems. In the end I just forked out $399 for a new 1u box to install my digium cards (BTW don't plugin in FXO lines to FXS, turns out it burns out the ports....).

And for software?

Time to try out Trixbox!

Trixbox is the new version of Asterisk@Home. The Asterisk@Home project recently changed their name, which to me was a brilliant idea. While I do see some home users of their project, I find that there are more business users. Trixbox is built on CentOS and comes with both MySQL and SugarCRM.
…

Trying to dig into what's been happening in MySQL-world over the last week and bumped into something that I've seen many times elsewhere, but did not expect to see on a site run by MySQL AB/Inc:

That is, of course, the error indicating that MySQL has reached it's connection limit and won't allow the page I requested to connect to the database to get the necessary information to display page 2.

Rumors are that there's an internal server infrastructure redesign underway. Maybe that includes the Planet/Forge server.

One of the ongoing problems with documentation at MySQL is that it is getting ever larger.

Not only is the size of the docs increasing, but the formats and languages that we support is increasing too, and that is making it more and more difficult to effectively list them and make sure they are available.

read more

I am in Portland this week for OSCON. I've got a couple of talks to
do this week (and a MySQL 5.1 Tutorial to do today).

I am a bit cavalier about short trips, I don't double check my
packing as much as I should. Therefor I neglected to pack my Treo's
charger. Last night I was thinking that I would need to get up this
morning and go buy a charger and then I remembered an article I read
on LifeHacker.com about hotels having boxes of power supplies just
sitting around collecting dust.

Its true!

This morning I went down to the front desk of the Double Tree and
asked if they had a box of chargers. Down to the basement they sent
me where I found not one box, but a few boxes of power supplies.

My Treo is now happily charging :)

Hi all -

Just a quick note to let you know that I’ve posted a new article on how to use MySQL 5.1 partitioning with date-based partition keys. Mikael Ronstrom already put up a nice blog post on this, and I figured I’d follow up with an article on the same subject since we’ve had a number of inquires.

Thanks (as always) for supporting MySQL!

I recently had to help a friend go through a site and correct alot of wrong URLs. Here is an easy way to do search and replace in MySQL, for those of you who didn’t know.

If you have phpMyAdmin you can use the SQL-tab to run this query. If not, you can run it from the commandline as well. Here is the query I ran: (remember of course to replace table_name, column_name, find_this and replace_with_this with real data)

UPDATE table_name SET column_name = replace(column_name,"find_this","replace_with_this");

[tags]MySQL,databases,sql,query[/tags]

Someone at work pointed out a rather interesting blog entry that purports to dump on MySQL Partitioning in a rather big way.In my opinion, he raises one valid point, but as for the rest of what he says, he's either misguided or misinformed. Except where he's Just Plain Wrong. Why? Let me give some reasons... He seems to be confusing Partitioning with Cluster. NDB Cluster does use partitioning (and has done so since before it was part of MySQL), but in 5.1 it's possible to use partitioning with most other storage engines, no Cluster necessary. (This is what's actually "new" about it in 5.1.) Whether he's talking about Cluster or about Partitioning (it's not clear which is the case), his contention that every box ... contains the whole database is simply wrong. He is correct in saying that you can't add or drop Cluster nodes online. This is being worked on. I can't say whether it'll make it into 5.2 (I personally doubt it, but I could be wrong about …

Someone at work pointed out a rather interesting blog entry that purports to dump on MySQL Partitioning in a rather big way.In my opinion, he raises one valid point, but as for the rest of what he says, he's either misguided or misinformed. Except where he's Just Plain Wrong. Why? Let me give some reasons... He seems to be confusing Partitioning with Cluster. NDB Cluster does use partitioning (and has done so since before it was part of MySQL), but in 5.1 it's possible to use partitioning with most other storage engines, no Cluster necessary. (This is what's actually "new" about it in 5.1.) Whether he's talking about Cluster or about Partitioning (it's not clear which is the case), his contention that every box ... contains the whole database is simply wrong. He is correct in saying that you can't add or drop Cluster nodes online. This is being worked on. I can't say whether it'll make it into 5.2 (I personally doubt it, but I could be wrong about …

One nice feature added for EXPLAIN statement in MySQL 4.1 is EXTENDED keyword which provides you with some helpful additional information on query optimization. It should be used together with SHOW WARNINGS to get information about how query looks after transformation as well as what other notes optimizer may wish to tell us. It is best seen by example:

PLAIN TEXT SQL:

1. mysql> EXPLAIN extended SELECT * FROM sbtest WHERE id>5 AND id>6 AND c="a" AND pad=c;
2. +----+-------------+--------+-------+---------------+---------+---------+------+--------+-------------+
3. | id | select_type | TABLE  | type  | possible_keys | KEY     | key_len | ref  | rows   | Extra       |
4. +----+-------------+--------+-------+---------------+---------+---------+------+--------+-------------+
5. |  1 …

Running EXPLAIN for problematic queries is very powerful tool for MySQL Performance optimization. If you've been using this tool a lot you probably noticed it is not always provide adequate information. Here is list of things you may wish to watch out.

EXPLAIN can be wrong - this does not happen very often but it does. EXPLAIN may not be telling you the truth, or full truth about query execution. The reason is - MySQL does not really have the special "plan generating" step, instead plan is generated as a part of query execution, sometimes being dynamic based on data. With EXPLAIN MySQL kind of simulates execution but it obviously does not access the data so does not have access to this dynamic component. If you suspect EXPLAIN is lieing you you can use SHOW STATUS "Handler" statistics to see if number of operations match.

EXPLAIN works for SELECT only This is in works to be fixed …