Bug 122345 - collectiondb cannot insert items contain non-latin chars
Summary: collectiondb cannot insert items contain non-latin chars
Status: RESOLVED DUPLICATE of bug 122168
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-20 14:05 UTC by LuRan
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LuRan 2006-02-20 14:05:21 UTC
Version:           svn snapshot (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.1.0 snapshot 
OS:                Linux

Just svn updated yesterday, after rebuild the collection, all the songs have non-latin chars in their tags or path is lost. and amarok gives error messages like this:

amarok:     [CollectionDB] [ERROR!] [virtual int SqliteConnection::insert(const QString&, const QString&)]  sqlite3_compile error:
amarok:     [CollectionDB] [ERROR!] unrecognized token: "'�
amarok:     [CollectionDB] [ERROR!] on insert: INSERT INTO tags_temp ( url, dir, createdate, modifydate, album, artist, genre, year, title, composer, comment, track, discnumber, sampler, length, bitrate, samplerate, filesize, filetype ) VALUES ('/home/hooey/video/anison/Drama CD 空の境界「俯瞰風景」/18_ソラヲコエテ.mp3','/home/hooey/video/anison/Drama CD 空の境界「俯瞰風景」',1136095463,1136095463,87,17,3,'8','ソラヲコエテENDING THEME', 18 , 0 , 0,125,128,44100,2005120,1)

Before the update I was using a snapshot fetched in a week before which works fine. So the bug must be introduced in the last week, probably the sqlite update?
Comment 1 Mark Kretschmann 2006-02-20 14:23:52 UTC

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