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 15856 - [IndexedDB] Remove empty string as a possible version
Summary: [IndexedDB] Remove empty string as a possible version
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Eliot Graff
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-02 16:37 UTC by Odin Hørthe Omdal
Modified: 2012-03-02 17:41 UTC (History)
4 users (show)

See Also:


Attachments

Description Odin Hørthe Omdal 2012-02-02 16:37:38 UTC
The spec references database version being the empty string. It's probably a leftover from older versions of the spec. But now the version is a unsigned  long, so it shouldn't be set to a string.


http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#object-store-concept

Change:
  When a new database is created it doesn't contain any object stores
  and has the empty string as version.
To:
  When a new database is created it doesn't contain any object stores.


http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#widl-IDBDatabaseSync-version

Change:
  This attribute has the empty string value when the connected database
  is first created.
To:
  This attribute is 0 when the connected database is first created.
Comment 1 Jonas Sicking (Not reading bugmail) 2012-03-02 17:41:42 UTC
Checked in http://dvcs.w3.org/hg/IndexedDB/rev/49374ca9ba89