[Webkit-unassigned] [Bug 29729] SQLiteTransaction should use BEGIN DEFERRED instead of BEGIN to begin read-only transactions

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=29729





--- Comment #9 from Michael Nordman <michaeln at google.com>  2009-09-25 14:59:27 PDT ---
(In reply to comment #8)
> Using SQLite patched in this way is a problem because we can no longer rely on
> the documentation when writing new code that uses SQLite.  Changing this
> instance to "BEGIN DEFERRED" may work around the current problem, but as new
> code is written and *correctly* uses only "BEGIN" it will be subtly incorrect
> in your configuration.  The solution there is not to insist that we always use
> "BEGIN DEFERRED" but to not change the behavior of SQLite in the first place.

Maybe the chrome team should re-visit its decision to apply the publicly
available patch to sqlite that has been applied. I'll mention this to brett.
But that chrome change seems a bit out-of-scope for this particular code
change.

BEGIN == BEGIN DEFERRED by default, so I still don't see any downside in the
context of this narrowly constrained code change.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.