/ View Ticket
Ticket UUID: ebde3f66fc64e21e61ef2854ed1a36dfff884a2f
Title: Shared cache has different busy behaviour than non-shared
Status: Closed Type: Feature_Request
Severity: Minor Priority: Immediate
Subsystem: Virtual_Machine Resolution: Works_As_Designed
Last Modified: 2014-03-11 13:04:06
Version Found In: 3.3.7

The shared cache immediately returns SQLITE_LOCKED instead of invoking the busy handler. There is an expectation that turning shared cache on or off would have no effect on existing code - ie it should neither need to know or care if shared cache is in use. The busy handling is a big difference.