[Webkit-unassigned] [Bug 153382] Modern IDB: SQLite backend needs to support simultaneous transactions

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 3 10:13:16 PST 2016


--- Comment #1 from Brady Eidson <beidson at apple.com> ---
My planned approach here was to:
1 - Have read-only transactions not actually backed by a SQLiteTransaction
2 - Allow only one writing transaction at a time
3 - Have the writing transaction open a new connection to the SQLiteDatabase, with a begin/end transaction around the write.

I started implementing this but quickly ran into the problem of when the write transaction was finally in progress, the database file was locked and therefore the read-only transactions started throwing "database locked" errors.

I *THINK* there's supposed to be a way around this with some mix of SQLite arguments (Making sure to use WAL mode along with some specific locking modes), but I am going to put this on the back burner for now.

Having "one transaction at a time" gives us parity with Legacy IDB, but Modern IDB is still way-way-way better in every *other* way, so this is not a regression.

Attaching my current patch to maybe revisit later.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160203/4fba1068/attachment.html>

More information about the webkit-unassigned mailing list