- From: Jonas Sicking <notifications@github.com>
- Date: Wed, 01 Jun 2016 12:30:38 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc:
Received on Wednesday, 1 June 2016 19:31:10 UTC
I'm surprised that is the case. Don't you guys just add an entry to an in-memory table when removing entries? And only once the transaction is committed write the deletion to LevelDB? Whereas if you need to return a count, you'd obviously need to go to LevelDB to read a count of the number of entries in the deleted range. That said, I'm really not particularly opinionated here. I'll just note that people tend to use whatever function meets their need and has the shortest name. So if there is a performance difference in the future, it's better to introduce `deleteWithCount()` now, than add `fastDelete()` later since `fastDelete()` would likely get very little usage. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/32#issuecomment-223099593
Received on Wednesday, 1 June 2016 19:31:10 UTC