JJZolx wrote: > Shouldn't the database just be locked while the one process is writing? > I imagine that the reason you can't write during a scan is that LMS > locks the database for writing the whole time by using one gigantic > transaction. > Can't find the post I think Andy or Michael did about this, but it's related to this bug report: http://bugs.slimdevices.com/show_bug.cgi?id=17609
A plugin that writes to the database while LMS is scanning can crash the scanner, so it's not just that the plugin is locked, depending on the timer the scanner will be locked from write access if the plugin is currently performing an operation. I don't know the details how WAL works, I can just describe that I had to make sure TrackStat didn't do any write operations during scanning because it either caused errors is TrackStat (which would be acceptable, but not good) or caused the scanner to crash (which is not acceptable). There were several issues also inside the LMS code regarding it in the 7.7 beta testing and I believe some of the bundled LMS plugins have also disabled or queued their write access during scanning to avoid the issue. ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=89450 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
