Question: I am trying to delay the link attrib so that it is applied after the content has faded out. But adding a timeout function does not work. Any ideas?

```
$(function () {
    $(".layout a").click(function () {
        setTimeout(function () { $("link:first").attr("href", $(this).attr('rel')); }, 500)
    $.cookie("Layout", $(this).attr('name'), { expires: 365, path: '/media', secure: true });
    $('.content, .searchresults').fadeOut(500).delay(500).fadeIn(275);
        window.scrollTo(0, 0); // Scroll Window back to Top
        return false;
    });
});

```

Answer: 
If you are concerned with stomping over existing rows, you need to mysqldump it as follows:

```
MYSQLDUMP_OPTIONS="--no-create-info --skip-extended-insert"
mysqldump -uroot --ppassword ${MYSQLDUMP_OPTIONS} --databases mydatabase > C:\mydatabase.sql

```

This will do the following:

* remove `CREATE TABLE` statements and use only INSERTs.
* It will INSERT exactly one row at a time. This helps mitigate rows with duplicate keys

With the mysqldump performed in this manner, now you can import like this

```
mysql -uroot -p --force -Dtargetdb < c:\mydatabase.sql

```

Give it a Try !!!

**WARNING** : Dumping with `--skip-extended-insert` will make the mysqldump really big, but at least you can control each duplicate done one by one. This will also increase the length of time the reload of the mysqldump is done.
This sounds like it is much more complicated than you are describing.

If you do a backup the way you describe, it has all the records in your database. Then you say that you do not want to delete existing rows from your database and load from the backup? Why? The reason why the backup file (the output from mysqldump) has the drop and create table commands is to ensure that you don't wind up with two copies of your data.

The right answer is to load the mysqldump output file using the mysql client. If you don't want to do that, you'll have to explain why to get a better answer.