/ Timeline
Login

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

7 check-ins related to "detect-moved-db"

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: 369a23e0 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: 9c59f5af 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: 2b1884dc user: drh tags: detect-moved-db
2013-12-06
19:58
Add the SQLITE_READONLY_DBMOVED error code to the sqlite3ErrName() function. check-in: 7789f801 user: mistachkin tags: detect-moved-db
17:23
Only error out on a database file move when attempting to start a write transaction. Assume read transactions are still safe. And make the error SQLITE_READONLY_DBMOVED instead of SQLITE_IOERR_NODB. check-in: 28348f2a user: drh tags: detect-moved-db
15:37
Add code to detect if the database file is moved or deleted out from under SQLite and return an SQLITE_IOERR_NODB. check-in: 8759a8e4 user: drh tags: detect-moved-db
14:53
Version 3.8.2 check-in: 27392118 user: dan tags: trunk, release, version-3.8.2