W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

Re: [IndexedDB] What happens when the version changes?

From: Nikunj Mehta <nikunj@o-micron.com>
Date: Thu, 13 May 2010 07:51:44 -0700
Cc: public-webapps WG <public-webapps@w3.org>
Message-Id: <B44F373A-1B32-41C7-9597-A60A11FA99D3@o-micron.com>
To: Shawn Wilsher <sdwilsh@mozilla.com>
If you search archives you will find a discussion on versioning and that we gave up on doing version management inside the browser and instead leave it to applications to do their own versioning and upgrades.

On May 12, 2010, at 11:02 AM, Shawn Wilsher wrote:

> Hey all,
> A recent concern that we have come across at Mozilla is what happens when the version changes?  Do we silently continue to work and hope for the best?  Do we throw an error every time saying that the version this database was opened with is no longer the version of the database?  It's not at all clear on what we should be doing in the spec, so we'd love to hear thoughts on this.  (We don't have a solution we are happy with yet to this problem either, so other options would be great).
> Cheers,
> Shawn
Received on Thursday, 13 May 2010 14:52:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:07 UTC