Registered Member
|
The new Amarok 2.1 beta was getting very confused with my collection (some tracks were showing up with wrong artists and albums, and other tracks were missing), so I wanted to rebuild my database from scratch. Only, I didn't want to lose years' worth of statistics that I've been building since the days of Amarok 1.3. MySQL to the rescue!
# First, copy your existing, semi-screwed-up database to a temporary area:
# Now blow away Amarok's copy of your database:
# Optionally, you can destroy all of Amarok's config, too:
# Optionally, you can tell MySQL Embedded not to bother initializing InnoDB, since # Amarok doesn't use it anyway, and it just wastes memory, time, and disk space.
# Now start Amarok and wait for it to rebuild your whole collection from scratch.
# Once it's finished, fully quit Amarok. (Be sure it's not still in the tray!) # Now copy the newly built database to the temporary area:
# To do the magic, we're going to need to start a MySQL server in that temp dir:
# (You might need to type /usr/sbin/mysqld instead of just mysqld.) # Now in another terminal, start up the MySQL client:
# And issue this gnarly query:
# Don't panic. It'll take quite a while to run for large collections. # Once the query is finished, you can exit the MySQL client and terminate the server:
# All that remains is to copy the populated statistics table back to Amarok:
# And clean up:
Last edited by whitslack on Sat May 16, 2009 8:54 am, edited 1 time in total.
|
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]