Closed
Bug 842649
Opened 13 years ago
Closed 4 years ago
Remove custom statement cache and use mozStorage's statement cache
Categories
(Core :: Storage: IndexedDB, defect, P5)
Core
Storage: IndexedDB
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bent.mozilla, Unassigned)
Details
IndexedDB started caching statements before it was cool but now there's a generic mechanism in moz storage. We shouldn't need two statement caching mechanisms.
Updated•8 years ago
|
Priority: -- → P5
Comment 1•4 years ago
|
||
Following the LSNG work, IDB's caching implementation was factored out into https://searchfox.org/mozilla-central/source/dom/quota/CachingDatabaseConnection.h and it is likely not suitable for upstreaming into mozStorage based on the tight integration with QM_TRY and the DOM: LWS team pointer guidelines which have not been adopted by mozStorage and are likely not something Places wants to adopt.
That said, appropriate use of and unification with mozStorage abstractions has happened, for example, mozStorageStatementScoper is used.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•