-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add IDBCursor.close() #185
Comments
TPAC 2019 Web Apps Indexed DB triage notes: We are in favor, especially as we're already tweaking the IDBCursor interface in V3. |
This would be easiest to define and test if we allow calling Otherwise, it's racy: there could be an outstanding @aliams @pwnall @asutherland - does that restriction sound acceptable? |
SGTM. |
SGTM! |
TMSG. (To me, sounds good!) |
TPAC 2024: We revisited this topic, which still seems like a good addition. Additional data and use cases would help browsers prioritize an implementation. |
Cursors require maintaining a fair bit of state. Implementations may also do optimizations such as pre-fetching records. This state can only be completely released when either the cursor hits the end of its range or both the request and the cursor have been GC'd (since there's an implicit bidirectional dependency), or when the transaction ends.
It might be nice to expose a
close()
method on cursors to allow web apps to signal that a cursor can be tidied up prior transaction closing.The text was updated successfully, but these errors were encountered: