Bug 122332

Summary:	MySQL database messed up after collection rescan
Product:	[Applications] amarok	Reporter:	Heiko Schaefer <heiko>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Heiko Schaefer 2006-02-20 11:13:52 UTC

Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs

I noticed that my MySQL-DB is messed up after a collection rescan.

I have a lot (almost most) of music stored on DVDs and CDs and added /media/dvd to the directories to scan. If I put in a DVD (or CD) and the collection is rescanned, it seems that the complete database is rebuilded and all former data is lost.

This results in lost lyrics, lost related artists, etc.

Is it possible only to add/update the new/changed entries, keeping the old ones?
Maybe with an extra function "Remove non-existent songs" only for the database? Or/and setting a flag, that the directory points to a removeable media.

I would like to have amaroK keeping my entries even if I remove the media.

I didn't checked this problem with other DBs (like sqlite or postgres).

Comment 1 Alexandre Oliveira 2006-02-20 12:13:09 UTC


*** This bug has been marked as a duplicate of 87391 ***