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

Re: [indexeddb] IDBRequest.transaction property set to null

From: Jeremy Orlow <jorlow@chromium.org>
Date: Mon, 27 Jun 2011 23:58:34 -0700
Message-ID: <BANLkTimj8G_TNOoTYGAE9d0QsXRYQJom+A@mail.gmail.com>
To: Israel Hilerio <israelh@microsoft.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
On Thu, Jun 23, 2011 at 2:21 PM, Israel Hilerio <israelh@microsoft.com>wrote:

> In the definition of IDBRequest.transaction it stipulates that "This
> property can be null for certain requests, such as for request returned from
> IDBFactory.open and IDBDatabase.setVersion."  Based on this we understand
> that the following handlers will set the transaction property to null:
> * setVersion onsuccess handler
> * setVersion onerror handler
> * setVersion onblock handler
> * open onsuccess handler
> * open onerror handler
> Are there any other times when this property should be set to null or is
> this the complete list?  We couldn't think of any other times when this
> applied but wanted to check.
>

I believe this is correct.


> Also, in the setVersion case, if we're setting the result property to its
> active transaction, why are we setting the transaction property to null
> instead of the same active transaction?
>

I know Jonas and I talked about this, but I don't remember the reasoning for
sure.  One thing I can think of off the top of my head is that it's weird
that it'd start off null and then be set later.  Also, it would be duplicate
data given that .result is also set to the transaction.  Is there any strong
reason to set it?

J
Received on Tuesday, 28 June 2011 06:59:02 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:45 GMT