Problems with sqlite support with 1.4.8: no such table: uniqueid_temp

[Rich]

On 2008.02.24. 18:16, Colin Guthrie wrote:
> Hi Guys,
> 
> 
> I'm just writing to ask some advice relating to a bug I'm seeing in
> Amarok 1.4.8.
> 
> 
> The full bug report is here but I'll summarise below:
> http://qa.mandriva.com/show_bug.cgi?id=37679
> 
> When using the Mandriva Cooker amarok package, the collection scanner
> seems to take a *very* long time to run and the CPU is maxed out during
> this process.
> 
> Building with debug and running via the console, I see repeated errors
> of the form:
> amarok:       [CollectionDB] [ERROR!] no such table: uniqueid_temp
> amarok:       [CollectionDB] [ERROR!] on query: SELECT uniqueid FROM
> uniqueid_temp WHERE deviceid = n AND url = './path/to/file.mp3';

i saw the same messages yesterday on a completely clean slackware 
install and 1.4 svn branch, revision 778156.

i didn't pay much attention to those, as i assumed it was because of the 
initial scan - but looking at the messages, they refer to _temp tables, 
which should have been created, should they not ?

for me, deviceid in those messages is '-1' (even though i haven't 
explicitly disabled dynamic collection and all the settings are defaults).

i'm on p3/733, so arch doesn't seem to make a difference here :)

> Switching to a MySQL backend allowed the collection scanner to run
> fairly quickly and it seemed to complete without error.
> 
> I hacked the collectiondb.cpp file to put in some additional debug and
> the call to createTables() with the temporary flag set to true is
> definitely called prior to scanning and the corresponding dropTables()
> call is not run before scanning so from a code flow perspective, things
> appear to be correct. I can only assume that there is some sort of
> non-committed transaction with SQLite (I think I've seen this before
> with temporary tables in another app), or some sort of threading issue.
> 
> I notice that there is a warning if when you try to use the system
> sqlite libs, so I ensured my test build did not use this and used the
> version included in amarok. This did not make any difference however :(
> 
> I'm quite happy to use MySQL but from a packaging perspective I'd like
> to try and solve this for other users.
> 
> It seems a similar issue was reported a while back:
> http://mail.kde.org/pipermail/amarok/2006-August/001020.html
> 
> Which Jeff Mitchell looked into and thought was resolved but the thread
> seemed to dry up there without any confirmation.
> 
> I'm on x86_64 just in case that makes some difference.
...
-- 
  Rich