Repository navigation
deleteDatabase error case should never happen #74
Description
The steps for deleteDatabase start off with
- Let request be a new open request.
- Queue a task to run these substeps:
- Let result be the result of running the steps for deleting a database, with the origin of the IDBEnvironment used to access this IDBFactory, name, and request.
- If result is an error set the error of request to result and dispatch an event at request. The event must use the Event interface and set the type attribute to "error". The event does bubble but is not cancelable.
But the "steps for deleting a database" never return an error. This may be legacy from timeout and/or sync behavior?
Activity
sicking commentedon Apr 18, 2016
Possibly. The only reason I can think of is file IO error.
I have no other recollection.
nolanlawson commentedon Sep 23, 2016
Is this just an implementation bug that this actually does throw? I'll double-check, but I'm pretty sure some engines (Edge iirc) throw if you rapidly open/delete databases with the same name several times.
inexorabletash commentedon Sep 23, 2016
We may want to keep this in the
deleteDatabase()steps, but add something into "steps for deleting a database" to allow implementations to generate errors.This is similar to the "forced close" addition; in the abstract it should never be needed, but in the real world implementations run into problems and how the errors appear to scripts should be defined.
Define how implementations should fail open/deleteDatabase. For #74