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

[Jeff Mitchell]

On Monday 25 February 2008, Rich wrote:
> On 2008.02.25. 11:56, Maximilian Kossick wrote:
> > This has nothing to do with the original problem (error in a sql query).
> > If the files that are mentioned in the query are actually stored on a
> > local disk (this includes usb disks), a deviceid of -1 means that a)
> > amarok could not connect to the kded mediamanager, or b) mediamanager is
> > returning incorrect data. As usual, run "dcop kded mediamanager fullList"
> > to find out what's going on.
>
> thanks, i already had forgotten the debugging skills on this :)
> it was pretty damn late when i finally got to collection building, so i
> just noted that down for later checking, which i hopefully will try
> tonight.

Also, Rich, do you have the actual same symptoms as Colin?  To wit:

"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."

Or do you just also see those messages in the console but the collection 
scanner is just fine?  And, Rich, are you also on Mandriva?

Colin, you may want to play around with different versions of sqlite 
(using --external-sqlite in configure, or changing the version inside the 
Amarok source tree).  Amarok is currently shipping with 3.4.1, from 
2007-07-24.  This was upgraded from 3.4.0 on 2007-06-19, 3.3.17 on 
2007-05-04, and so on (svn log on sqlite3.h in src/sqlite shows the dirt).  
So if your problem started happening at some point around those times, try 
downgrading.  If, on the other hand, your errors just started happening 
recently, then maybe something else on your system is having issues and 
interacting with sqlite in a bad way.

--Jeff