After a long hiatus, I am happy to announce that mylvmbackup version 0.12 has now been released. This release includes a large number of improvements, minor code cleanups, as well as some new functionality. In particular, I would like to thank Matthew Boehm, Tim Stoop, Baron Schwartz, Ville Skyttä and Ronald Bradford for their contributions.

Some notable highlights from the ChangeLog:

• Removed the absolute path names to external tools (make sure $PATH is correct)
• Added --log-err to the startup options of the recovery instance to avoid cluttering the server's error log
• Added support for hooks written as Perl Modules. (Matthew Boehm)
• Added support for date/time-formatted path names for backupdir and mountdir (Matthew Boehm)
• Backupdir and …

I continue to try and find new ways to make it easier for people to get into the right place in the documentation for the information you are looking for.

This week, I’ve added some experimental custom indexes. These use information from the ID mapping process that we use in lots of parts of the documentation to do some interesting stuff.

The indexes are an extension of the other areas where we already provide summaries (like the list of options/variables, or functions). These provide quick access into the definition of the function, but not a link to where that function might have been mentioned elsewhere in the documentation. With the indexes, we’ve extended that so that you can now see all of the places within the reference manual where we mention a specific function. This goes beyond the index (which relies on us adding specific tags), and just lists everywhere that we mention a specific option.

Currently …

I will co-present in webinar on Performance Challenges and Solutions for IO Bound Workloads in MySQL. My part of the presentation will be speaking about why switching from CPU bound workload to IO bound is such an important event, how to prepare to it as well as how to keep your application performance good as the data growths.

The Brian's portion of webinar will focus on the Schooner offering as example of flash based appliance - one of solutions I mention in my presentation.

It should be interesting whenever you're interested in Schooner appliance offerings, flash or scaling MySQL in General.

You can follow this url to register.

Entry posted by peter | …

When writing queries, try making a habit out of using short table aliases, no matter how small the query is. Try using an alias that is as short as possible (one letter if possible, two or three when necessary) to avoid clutter in your queries.
Use these aliases in all places where you refer to a field, no matter if it would technically not be necessary. It will make your queries readable, and if you later need to join in other tables, you will not run the risk of ambiguous field names.

Let’s look at an example using the World database. The following two queries both select the 10 biggest cities by population in the continent of Africa, with a population between 1 and 1,5 million.

Good practice:

SELECT
  ci.name AS city_name,
  ci.district,
  co.name AS country_name,
  ci.population
FROM
  Country AS co
  INNER JOIN City AS ci ON …

As you may know, Iranian citizens do not have internet as the government has blocked almost all the websites (as well as phone calls and SMSs).
To help the Iranian people get information, please consider installing and using Tor to allow Iranians to anonymize themselves and see blocked websites.
سایت های اینترنت توسط دولت ایران مسدود شده است. به مردم ایران برای دیدن سایتهای مسدود شده با استفاده از یک برنامه خاص کمک کنیدTor







After installing you can help more effectively by providing your tor details directly to Iranian citizens by following this …

Over at phpdeveloper.org I was pointed to a blog post talking about MySQLi and stored procedures. That reminded me about a small thing I recently did: When using MySQLi's multi_query to send queries which return multiple result sets you have to use a rather unintuitive API which can certainly be improved.

Recently I sat down and cooked up a small improvement for that, being an iterator fan I, of course, had to use an iterator for that and implemented the following class:

<?php
class MySQLi_ResultsetIterator implements Iterator {
    private $mysqli;
    private $counter = 0;
    private $current = null;
    private $rewinded = false;

    public function __construct(mysqli $mysqli) {
        $this->mysqli = $mysqli;
    }
    private function freeCurrent() {
        if …

Hi all!

I'm pleased to announce a release of DBD::mysql 4.012!

This release includes several fixes and modifications (per ChangeLog):

* Patch to bind_type_guessing from Craigslist, Thanks to Chris! Happiness is no quoted numbers. Fixed ChopBlanks to work with bind_type_guessing

* Patch for win32 strawberry build Thanks to Curtis Jewell! Windows needs love

* Patch for auto-reconnect to set active flag Thanks to Doug Fischer!

* Fixed bug 32464 http://bugs.mysql.com/bug.php?id=32464. See also: https://rt.cpan.org/Ticket/Display.html?id=46308
Add connection flag mysql_no_autocommit_cmd which users of MySQL Proxy can use to prevent 'set autocommit=#' from being issued by the driver. 'perldoc DBD::mysql' to …

I am currently working on a 2.4 version of MyQuery. I have included a few cool features in it, and I have also done some significant changes to the code.
Above all, all database access function has been put in one single file with a set up functions to allow me to add other types of connections later. In the process, I have figured out a few things about the MySQL C API that I am not so hot on.
To take one example, I'm not too keen on the naming convention of fields and columns. It seems that, in the naming of functions in the API, someone seems to think that a column and a field is the same thing. They are not.
This is how many people look at things, including myself, when we speak of relational data:

• A row is one of 0 or more rows in a database.
• A column is one of 1 or more columns in a dataset.
• A field is the "crossing" of a row and a column.

Now, you are welcome to …

We’ve just released the second RC of the cross-platform version of MySQL Workbench. Version 5.1.14 is now available for download. We closed 5 bugs since last week and worked on more refinements. For the complete list of changes please take a look at our Releases Page.

Please head over to our Download page to give this release a try:

http://dev.mysql.com/downloads/workbench/5.1.html

End of next week we are going to build another RC release before we’re preparing the final GA release of Version 5.1. If you find bugs, please post it to our bugtracker. Feel free to contact us on IRC (irc.freenode.net, #workbench) for any questions or infos.

- The Workbench Team

I would like to start off by excusing myself for having had a broken link on http://www.securich.com/downloads.html when I published the latest blog post about Securich.

The tool is downloadable from there and anyone can use it for free in accordance to GPLv2.

I wanted to throw out tutorial about how to install it and use it (Note this tutorial is for version securich version 0.1.2):