--- [EMAIL PROTECTED] wrote:
> It may be more difficult to implement this in a backwards-compatible
> way such that older versions of SQLite can rollback a journal created
> by a newer version if it encounters one.
I wonder if there are many projects that have different versions of
SQLite updating and reading the same database file at the same time.
This can't be very common.
Perhaps if a new version of SQLite is killed mid-way through a nested
transaction and an older version tries to subsequently read the same
database, but this is pretty obscure.
Hypothetically, would an older version of SQLite change the database
file or journal file in any destructive way if it encountered a journal
format that it was not familiar with?
____________________________________________________________________________________
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
