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

[Jeff Mitchell]

Colin Guthrie wrote:
> Jeff Mitchell wrote:
>   
>> 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.
>>     
>
> Well it seems the mdv package uses the external-sqlite anyway (I
> disabled it for testing with the "known good" version.
>
> I'll certainly try downgrading it to see if it's at fault.
>   
Okay.  Unfortunately, I tried this morning and still no luck.  I went 
from using 3.5.3 with external sqlite to 3.4.1 with included sqlite, and 
rescanned my collection, and could not reproduce the issue.

One thing I just thought of:  are you seeing these issues with a full 
scan (Rescan Collection), an incremental scan (Update Collection), or 
both?  If incremental, what are you doing to trigger the incremental change?

Thanks,
Jeff