>> Is there something particular going wrong under Windows?
>
> Yes, the corrupted database problem is only on Windows.
It might be related to long file names and how sqlite and/or perl deal
with them in this case. I modified the code to use short names instead of
what we're using now, and the scans run fine...
Jim - could you please run a test with the following minor changes applied
to SQLiteHelper.pm:
Index: SQLiteHelper.pm
===================================================================
--- SQLiteHelper.pm (revision 33055)
+++ SQLiteHelper.pm (working copy)
@@ -103,7 +103,7 @@
$source = "dbi:SQLite:dbname=$db";
}
else {
- $source = sprintf( $prefs->get('dbsource'), catfile(
$prefs->get('librarycachedir'), 'squeezebox.db' ) );
+ $source = sprintf( $prefs->get('dbsource'), catfile(
$prefs->get('librarycachedir'), 'sb.db' ) );
}
return $source;
@@ -133,7 +133,7 @@
# We create this even if main::STATISTICS is not false so that the SQL
always works
# Track Persistent data is in another file
- my $persistentdb = $class->_dbFile('squeezebox-persistent.db');
+ my $persistentdb = $class->_dbFile('sb-p.db');
push @{$sql}, "ATTACH '$persistentdb' AS persistentdb";
push @{$sql}, 'PRAGMA persistentdb.journal_mode = WAL';
Basically rename squeezebox.db to sb.db, and squeezebox-permanent.db to
sb-p.db. Then wipe the Cache folder and try again? Thanks!
Erland - are any of your tools depending on that file name? Would you see
any issue with any of them if we applied above change?
--
Michael
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
