Some things to consider:
(1) VACUUM is never necessary, though can sometimes reduce the size of the
database file and provide a performance improvement if the database is large
and fragmented.
(2) Use PRAGMA freelist_count to estimate how much VACUUM will shrink a
database.
(3) VACUUM requires
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Would it possibly be more appropriate and expedient to only provide a
sync API for now (and defer async support to possibly a later
version)? It seems like the design of IndexedDB is such that most
operations should occur in O(log n) time, and
On Fri, 12 Mar 2010 22:31:15 +0100, Dirk Pranke dpra...@chromium.org
wrote:
I admit to not being super familiar with the spec as it currently
stands, but I find the idea that we would add something like this
fairly unappealing. I'm not familiar with any other database API
that asks the