SQLite: View Ticket

2014-03-11
13:14		• Closed ticket [61d35ac210]: A way to tell if a journal should exist plus 3 other changes (artifact: 8cfcaee08e user: drh)
2009-11-10
23:31		• Ticket [61d35ac210]: 3 changes (artifact: 24ad0a80d7 user: rogerb)
2009-10-23
08:31		• New ticket [61d35ac210]. (artifact: 7b540e42f5 user: rogerb)

Ticket Hash:	61d35ac2104ec81bd1b7ce787b22a9491fceddff
Title:	A way to tell if a journal should exist
Status:	Closed	Type:	Feature_Request
Severity:	Important	Priority:	Immediate
Subsystem:	Unknown	Resolution:	Rejected
Last Modified:	2014-03-11 13:14:00 11.32 years ago	Created:	2009-10-23 08:31:57 15.70 years ago
Version Found In:	3.3.13

Description:

http://www.sqlite.org/cvstrac/tktview?tn=2224

To aid in troubleshooting there should be a documented way when provided with a database to determine that there should also be an accompanying journal.

rogerb added on 2009-11-10 23:31:36:
In addition there should also be some way to check that a particular journal actually matches the database. Consider the case of a journal being backed up and later restored but mismatching the database by a few seconds. Replaying that journal will corrupt the database.

A suggestion from Scott Hess on the mailing is that the journal could store the file change counter.