Bug 127168 - scanning collection wipes out database (mysql)
Summary: scanning collection wipes out database (mysql)
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 1.4-SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-11 21:55 UTC by Alan Ezust
Modified: 2008-08-04 19:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Ezust 2006-05-11 21:55:27 UTC
Version:           1.4-SVN (using KDE 3.5.2, Debian Package 4:3.5.2-2+b1 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.14-kanotix-9

I have a collection and while it is scanning and adding to a mysql database, it prints out these messages:

amarok: FAILED QUERY: SELECT id, name FROM year_temp WHERE name  LIKE '0' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.genre_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM genre_temp WHERE name  LIKE 'General Classical' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.year_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM year_temp WHERE name  LIKE '0' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.genre_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM genre_temp WHERE name  LIKE 'General Classical' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.year_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM year_temp WHERE name  LIKE '0' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.genre_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM genre_temp WHERE name  LIKE 'General Classical' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.year_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM year_temp WHERE name  LIKE '0' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.genre_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM genre_temp WHERE name  LIKE 'General Classical' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.year_temp' doesn't exist
amarok: FAILED QUERY: SELECT id, name FROM year_temp WHERE name  LIKE '0' ESCAPE '/' ;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.tags_temp' doesn't exist
amarok: FAILED QUERY: SELECT DISTINCT album.name FROM tags_temp, album_temp AS album WHERE tags_temp.dir = '/mnt/music/ByGenre/WorldAmbient/Wim Mertens/Maximizing The Audience' AND album.id = tags_temp.album AND tags_temp.sampler IS NULL;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Table 'amarok.tags_temp' doesn't exist
amarok: FAILED QUERY: UPDATE tags_temp SET sampler = 0 WHERE sampler IS NULL;
amarok:     BEGIN: void CollectionDB::copyTempTables()
amarok:     END__: void CollectionDB::copyTempTables() - Took 0.0085s
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'tags_temp'
amarok: FAILED QUERY: DROP TABLE tags_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'album_temp'
amarok: FAILED QUERY: DROP TABLE album_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'artist_temp'
amarok: FAILED QUERY: DROP TABLE artist_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'genre_temp'
amarok: FAILED QUERY: DROP TABLE genre_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'year_temp'
amarok: FAILED QUERY: DROP TABLE year_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'images_temp'
amarok: FAILED QUERY: DROP TABLE images_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'embed_temp'
amarok: FAILED QUERY: DROP TABLE embed_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'directories_temp'
amarok: FAILED QUERY: DROP TABLE directories_temp;
amarok:     [CollectionDB] MYSQL QUERY FAILED: Unknown table 'uniqueid_temp'
amarok: FAILED QUERY: DROP TABLE uniqueid_temp;
amarok:   END__: virtual bool ScanController::doJob() - Took 6.7e+02s
amarok: END__: virtual void ThreadWeaver::Thread::run() - Took 6.7e+02s
amarok: [CollectionDB] JobFinishedEvent from ScanController received.
amarok: [ContextBrowser] Rendering showCurrentTrack()
amarok: BEGIN: void CollectionView::renderView(bool)
amarok:   current browser is not collection, aborting renderView()
amarok: END__: void CollectionView::renderView(bool) - Took 0.00011s
amarok: [ThreadWeaver] Job completed: CollectionScanner. Jobs pending: 0
amarok: BEGIN: virtual ScanController::~ScanController()
amarok: END__: virtual ScanController::~ScanController() - Took 0.00018s
amarok: [virtual KDE::ProgressBar::~ProgressBar()]
amarok: [ThreadWeaver] Threads in pool: 2
amarok: [xine-engine] XINE_EVENT_UI_SET_TITLE
amarok: [xine-engine] Metadata received.
amarok: BEGIN: void EngineSubject::newMetaDataNotify(const MetaBundle&, bool)
amarok:   [Scrobbler] It's still the same track.
amarok:   [ContextBrowser] Rendering showCurrentTrack()
amarok: END__: void EngineSubject::newMetaDataNotify(const MetaBundle&, bool) - Took 0.18s
amarok: [ThreadWeaver] Threads in pool: 2
amarok: BEGIN: void CollectionView::renderView(bool)
amarok: END__: void CollectionView::renderView(bool) - Took 0.0059s


at this point, the database is wiped out.
Comment 1 Mark Kretschmann 2006-05-11 22:18:41 UTC
What MySQL version?
Comment 2 Alan Ezust 2006-05-11 22:24:11 UTC
mysql  Ver 14.12 Distrib 5.0.20a, for pc-linux-gnu (i486) using readline 5.1
mysqld  Ver 5.0.20a-Debian_2-log for pc-linux-gnu on i486 (Debian Etch
distribution)
libmysql15-dev


On 11 May 2006 20:18:45 -0000, Mark Kretschmann <markey@web.de> wrote:
[bugs.kde.org quoted mail]
Comment 3 Seb Ruiz 2006-05-12 06:51:49 UTC
This means that credentials to the database are incorrect.

You should check them, in amarokrc and try log in using
$> mysql -u USERNAME -p DATABASENAME
Comment 4 Alan Ezust 2006-05-12 19:56:27 UTC
I tried importing a directory with over 14,000 songs in it, and it caused this problem. When I imported each directory individually, I could not reproduce this problem. And it's really hard to reproduce anyway, so I don't know what to do. I am looking at the database code more closely now though, and if I notice some (more) specific buggy SQL statements I'll let you know. 

Comment 5 Myriam Schweingruber 2008-08-04 19:25:09 UTC
Closing du to lack of feedback, assumed to be fixed for the user.