Re: IndexedDB Versions

On Wed, Jul 17, 2013 at 5:20 AM, Mahon <mbbaldwin@gmail.com> wrote:
> I am wondering why versions are required in the IndexedDB specification. If
> I'm reading the specification correctly if you want to add or remove objects
> or idecies then you need to increment your database version number. Perhaps
> I'm wrong, but this seems to be rather arbitrary. It makes more sense to me
> that there would be no version at all, but there would be a way to
> programmatically determine if an object store exists or if an index exists.

We could have done that, but that would have meant that it would have
required an asynchronous operation to start a transaction. As things
stand we were able to synchronously return a Transaction object, which
you immediately can use to place requests.

Not sure if we made the right decision to be honest, since you still
always have to fight with opening the database being an async
operation.

But that's what we did. It's too late to change now, unless you can
propose a way to change things in a backwards compatible way.

/ Jonas

Received on Wednesday, 17 July 2013 22:26:37 UTC