This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11425 - [IndexedDB] Transaction timeout parameter should probably be a double
Summary: [IndexedDB] Transaction timeout parameter should probably be a double
Status: RESOLVED DUPLICATE of bug 11552
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-webapps-bugzilla
: 10590 (view as bug list)
Depends on:
Reported: 2010-11-29 11:47 UTC by Jeremy Orlow
Modified: 2011-01-25 22:32 UTC (History)
2 users (show)

See Also:


Description Jeremy Orlow 2010-11-29 11:47:55 UTC
Right now, the transaction timeout parameter is an unsigned long with no time equivalent to infinity and no way (other than omission) to use the browsers default.  Unsigned long is also kind of an odd type to use in a JavaScript API.

Maybe this should be a double instead.  Positive infinity could mean "no timeout".  0 and/or negative could mean browser default and/or throw an exception.  (I don't care much either way.)

Note that Geolocation uses a double for their timeout parameter.  In that case, 0 means to timeout immediately if there's no cached value.  In IndexedDB, it seems as though the analog would be like a try lock (i.e. run the transaction if we can without waiting at all), but I'm not sure that has much benefit and it would be adding non-deterministic surface area which seems bad.
Comment 1 Jeremy Orlow 2010-12-10 12:21:26 UTC
*** Bug 10590 has been marked as a duplicate of this bug. ***
Comment 2 Jeremy Orlow 2011-01-25 22:32:40 UTC

*** This bug has been marked as a duplicate of bug 11552 ***