We should remove DBConnection from nsIFormHistory.idl.

RESOLVED WONTFIX

Status

Cloud Services
Firefox Sync: Backend
RESOLVED WONTFIX
7 years ago
7 years ago

People

(Reporter: espindola, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

And use a higher level function to create the statements so that they can be finalized.
I think this is likely a WONTFIX... Bug 566746 is going to add async APIs that Sync should be able to use instead of the raw DB connection. I'm not planning on removing the DB connection (since it's often useful for tests), but I could be convinced otherwise if there's a reason!
(In reply to Justin Dolske [:Dolske] from comment #1)
> I think this is likely a WONTFIX... Bug 566746 is going to add async APIs
> that Sync should be able to use instead of the raw DB connection. I'm not
> planning on removing the DB connection (since it's often useful for tests),
> but I could be convinced otherwise if there's a reason!

The reason behind removing the connection is that, until we implement bug 702559, we don't have a "safe" connection to expose to add-ons.
Practically now we could fix all internal Storage users so that they don't cause thread contention (and Bug 566746 is going toward that direction), then a single add-on using your connection handle from the outside may reintroduce contention and thread-locking by using your internally-pure-async connection with the Storage synchronous API.
Surely, removing the connection may have a cost in terms of tests and existing add-ons using it, that I've not yet evaluated.
The patch in 702848 has been changed to use a "will close" callback. Closing this bug as Wontfix. We can reopen if something changes in 702848.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.