>After looking over your patch I have a question on how the incremental scanning
>will fix the GUI assert issue?
The patch I just submitted has nothing to do with incremental scanning.
All it does it recover better from a locked database, so that the assertion is
never reached.
>As I see it the db will be committed to at random for a short amount of time,
>if your assumption is correct that a table is blocked for reading during a
>transaction this block will only be lifted shortly and it is nearly impossible
>to get read access during that time.
It would seem safe to assume that sqlite3 processes access-requests in the
order received, and so as soon as a write commits its changes, all pending
access-requests get processed before a new one (i.e. the library-scanner's next
attempt to open a write transaction) is allowed to lock the table again.
Steven Boswell
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
