Documentation Source Text

Check-in [9a56445dbf]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Minor update to unlock_notify.in.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 9a56445dbf5e97ac59f4578cfce10458566d45f5
User & Date: dan 2009-03-13 16:08:01
Context
2009-03-16
13:34
Tweaks to the sqlite3_unlock_notify() documentation. check-in: 14a827286f user: drh tags: trunk
2009-03-13
16:08
Minor update to unlock_notify.in. check-in: 9a56445dbf user: dan tags: trunk
15:33
Add a page that illustrates use of the new experimental sqlite3_unlock_notify() API. check-in: f0a5786f01 user: dan tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/unlock_notify.in.

246
247
248
249
250
251
252
253
254



255
256
257
    left, this could cause an infinite loop.

  <p>
    The caller could distinguish between this special "DROP TABLE|INDEX" 
    case and other cases by using extended error codes. When it is appropriate
    to call sqlite3_unlock_notify(), the extended error code is
    SQLITE_LOCKED_SHAREDCACHE. Otherwise, in the "DROP TABLE|INDEX" case,
    it is just plain SQLITE_LOCKED.





<div style="clear:both"></div>








|
<
>
>
>



246
247
248
249
250
251
252
253

254
255
256
257
258
259
    left, this could cause an infinite loop.

  <p>
    The caller could distinguish between this special "DROP TABLE|INDEX" 
    case and other cases by using extended error codes. When it is appropriate
    to call sqlite3_unlock_notify(), the extended error code is
    SQLITE_LOCKED_SHAREDCACHE. Otherwise, in the "DROP TABLE|INDEX" case,
    it is just plain SQLITE_LOCKED. Another solution might be to limit

    the number of times that any single query could be reattempted (to say 
    100). Although this might be less efficient than one might wish, the 
    situation in question is not likely to occur often.

<div style="clear:both"></div>