I just upgraded Amarok from 2.1.1 to 2.2.0. On starting 2.2, it rescans the collection, and when it does, my old track statistics (play count, rating, etc.) aren't preserved. Instead, it seems that random statistics have been assigned to random tracks. Eg., tracks that I have never played or rated now have a play count and a rating.

Fortunately, I backed up the 2.1 database, so nothing is permanently lost.

I had also tried upgrading 2.1 to the 2.2 beta and then the RC, but both times I reverted to 2.1 as I had this same problem, which I thought would be resolved with the official release.

Is the 2.2 database not compatible with the 2.1 database, or am I doing something wrong? I really want to use the new version, but I also really don't want to lose 3 years' worth of statistics....

Further info:
I'm using KDE 4.3.1 on Mandriva 2009.1 (i586), and I got the new version from this repository:
ftp://ftp.caliu.cat/pub/mirrors/kde/stable/4.3.2/Mandriva/2009.1/i586/media/kde4

Also, the database I now have with 2.1 was imported from 1.4 using the 'import database' tool.

Database version number increased from 2.1 to 2.2.
But the random statistics still occurs in 2.2.1-git. I first thought, it was because of saving my statistics tables and copying them back after rebuilding my collection.
Database issues were a problem in 1.4 and are still.
I've had a power loss, while Amarok was running.
Because my collection is on a external disk, while Amarok kept running because of battery power, it ended up in a corrupt database.


m0nk

Dieter Schroeder wrote:Database version number increased from 2.1 to 2.2.

But isn't there any way of preserving old statistics for people who upgrade from 2.1?

See here.
I save my statistics tables, either as dumb or just the files, and write them back, if needed.

m0nk

That sounds like it'll be too difficult for me, as I have no knowledge of mysql.

Anyway, I guess I'll just have to wait and hope that a future version fixes this problem.

Thanks for your help, m0nk.

Dieter Schroeder wrote:Database version number increased from 2.1 to 2.2.
But the random statistics still occurs in 2.2.1-git. I first thought, it was because of saving my statistics tables and copying them back after rebuilding my collection.
Database issues were a problem in 1.4 and are still.
I've had a power loss, while Amarok was running.
Because my collection is on a external disk, while Amarok kept running because of battery power, it ended up in a corrupt database.

Blame MySQL for this joy.

Amarok currently needs to use the old MyISAM storage engine (which is not even ACID compliant), as the newer InnoDB does not support multi-threading. Grrr.

monk (or somebody) - the page you linked to just had a wishlist, was there a page with a description of how to dump your statistics from the amarok database in 2.1?

it seems that the only way to preserve our statistics will be to manual export them from the amarok 2.1 database, upgrade to 2.2, then manually import them? but what i'm wondering is how.... i've done basic mysql commands before, but would love some help with this!

thanks!
jetpeach

Correct, that was my wishlist. To backup my database, I use a script, which starts mysqld with datapath set to .kde(4)/share/apps/amarok/mysqle and and save it to .kde(4)/share/apps/amarok/backup (folder must exist). Atm I call it manually, because I have to kill it by its pid:

Code: Select all

#!/bin/sh
/usr/sbin/mysqld --defaults-file=`pwd`/my.cnf --default-storage-engine=MyISAM --datadir=`pwd`/mysqle --socket=`pwd`/sock --skip-grant-tables --skip-innodb --skip-networking &
sleep 5
mysqldump -S `pwd`/sock amarok > backup/amarok-`date +%d-%m-%Y-%k:%M`.sql

There's an option in krecipes to save the database, which would also be nice in amarok.

m0nk

Thanks mOnk! After some fiddling, I got it working to export from the database and back it up to a .sql file. Never figured out how to then import it to amarok 2.2 on my other computer, but found that after copying the mysqle folder from the 2.1 amarok computer to the 2.2, the second time it worked and my database has statistics and accurate song names (the first time the tags got all screwed.)
Anyway, I'm happy so thanks!

markey wrote:

Dieter Schroeder wrote:Database version number increased from 2.1 to 2.2.
But the random statistics still occurs in 2.2.1-git. I first thought, it was because of saving my statistics tables and copying them back after rebuilding my collection.
Database issues were a problem in 1.4 and are still.
I've had a power loss, while Amarok was running.
Because my collection is on a external disk, while Amarok kept running because of battery power, it ended up in a corrupt database.

Blame MySQL for this joy.

Amarok currently needs to use the old MyISAM storage engine (which is not even ACID compliant), as the newer InnoDB does not support multi-threading. Grrr.

Not really, I've been using Amarok with MySQL and switched the tables to InnoDB (not all can be converted) and it has worked great over the last few years.

Dieter, I'm willing to help convert the tables to InnoDB if you can point me to a wiki or any documentation online with information about the problems you might've found.

My $.02
G