Last month I blogged about the silly changes to the default for the SHOW STATUS command in MySQL 5.0 in Stop the madness: SHOW STATUS, and I filed MySQL Bug #19093: SHOW STATUS defaults to SESSION.

Well, it looks like Monty has spoken and this will not be fixed. That’s unfortunate, but oh well, I tried.

You can read the full text of Monty’s reply in the bug report itself, but his reasons for supporting the current behaviour boil down to:

• It’s similar to what SHOW VARIABLES does. — Yes, this is true, but neither commands’ output makes sense, really. If you do SHOW [SESSION] STATUS, you get a mix of session-scoped and global-scoped results back, and there’s no way to tell which is which. Same goes for SHOW [SESSION] VARIABLES. Ugh.
…

Test

I ran across this article while going through some of the articles on Planet MySQL. The article is about how to properly file a bug report. It’s very well written, you can find the article here. If you use software, you need to read this. (That means all of you do).

The post that took me to this article, is here.

Tags: bug reports,, software qa

T-Dose, the Technical Dutch Open Source Event, a kind of Fosdem but in Eindhoven has just released their Call for Papers / Participation.

Go and have a look at it.. they are looking at all kind of open source contributions, ranging from Linux on the desktop, Weird things to do with MySQL to Open Source Games.

Go read the CFP yourselves at the T-Dose site

On one hand I want to be there.. on the other hand .. I hope to miss T-Dose in favour of LiSA 06

Vani and I both started using "Life Balance":http://www.llamagraphics.com/LB/LifeBalanceTop.html for our todo lists in the last week or two. It's great so far.

One of the items I added was a occasionally recurring "File a bug report" task.

Writing a "good bug report":http://www.chiark.greenend.org.uk/~sgtatham/bugs.html is a relatively quick and easy way to help the authors and maintainers of the software you use make it better.

I was working a bit with "Xen":http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ on Fedora Core 5 some days ago and found out that the default scripts don't deal nicely with anything but the most basic net configuration. "Hello bugzilla":https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=193322.

MySQL is one of the nicest projects to file bug reports for, because they are very nice about "following up":http://bugs.mysql.com/bug.php?id=19498 and actually …

Vani and I both started using "Life Balance":http://www.llamagraphics.com/LB/LifeBalanceTop.html for our todo lists in the last week or two. It's great so far.

One of the items I added was a occasionally recurring "File a bug report" task.

Writing a "good bug report":http://www.chiark.greenend.org.uk/~sgtatham/bugs.html is a relatively quick and easy way to help the authors and maintainers of the software you use make it better.

I was working a bit with "Xen":http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ on Fedora Core 5 some days ago and found out that the default scripts don't deal nicely with anything but the most basic net configuration. "Hello bugzilla":https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=193322.

MySQL is one of the nicest projects to file bug reports for, because they are very nice about "following up":http://bugs.mysql.com/bug.php?id=19498 and actually …

I'm sure as a system administrator on any flavour of UNIX you appreciate the power of the few magic characters, such as #!/bin/sh, found at the first line of many scripts, commonly called a shebang. They allow you to treat a script almost as a binary executable. To run it, you just type its name at the prompt and don't have to worry if it's written in Perl, Bash, awk, Python or anything else. Just for your MySQL scripts you still type the verbose mysql < your_script.sql all the time, don't you?

I found this to become especially annoying (yes, programmers and administrators are lazy folks) now that every MySQL release gives me more and more powerful features: Where I before had to write a script in another language anyway, now I often find that MySQL allows me to do everything in plain SQL, even some complex data extraction tasks (using …

Hi All -

Just a quick note that I’ve written a follow up article on partitioning that’s in the MySQL Dev Zone article section for you to check out.  It shows how well defined segments of data can be easily managed and removed with partitioning.  Check it out if you get time and let me know how you’re using partitioning in MySQL 5.1 now!

Thanks,

–Robin 

DaveM talks about Ingo’s new SMP lock validator for linux kernel

A note reminding me to go take a look and see what can be ripped out and placed into various bits of MySQL and NDB. Ideally, of course, it could be turned into a LD_PRELOAD for pthread mutexes.

Anybody who wants to look deeper into it before I wake up again is welcome to (and tell me what they find)

In what I laughingly call “spare time” I started hacking on ha_file.cc, otherwise known as the FILE storage engine. My idea is relatively simple, I want to be able to store and access my photos from MySQL. I also want the storage to be relatively efficient and have the raw image files on disk, not tied up too much in any different format (my file system is pretty good at storing multi-megabyte files thank you very much) - it also doesn’t require any fancy things to re-use space when I delete things. I should also be able to (efficiently) directly serve the images out of a web server (satisfying the efficiency itch). You could also use something like DMF to migrate old rows off to tape.
So, I started some hacking and some designing and have a working design and a nearly basically working read/write implementation. I’ll share the code when it does, in fact, actually work (by “work” i mean reads and writes basic rows).
I’ve …