SQLite

Check-in [9c59f5af7a]
Login

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

Overview
Comment:Back out the new device capability. The determination of whether or not a file has moved is now done strictly using a file-control.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | detect-moved-db
Files: files | file ages | folders
SHA1: 9c59f5af7ac4908583fab85d37241f200c40f02d
User & Date: drh 2013-12-07 16:45:05.762
Context
2013-12-07
16:56
At the start of each journaled write transaction, check to see if the database file has been moved, and if it has refuse to start the transaction, returning an SQLITE_READONLY_DBMOVED error code. Writing to a moved or renamed database is still allowed when journal_mode is OFF or MEMORY. (check-in: 369a23e006 user: drh tags: trunk)
16:45
Back out the new device capability. The determination of whether or not a file has moved is now done strictly using a file-control. (Closed-Leaf check-in: 9c59f5af7a user: drh tags: detect-moved-db)
12:29
Actually look at i-node numbers to determine whether or not the database file has moved. (check-in: 2b1884dc14 user: drh tags: detect-moved-db)
Changes
Unified Diff Side-by-Side Diff Patch
Changes to src/os_win.c.
Changes to src/pager.c.
Changes to src/sqlite.h.in.