RE: [IndexedDB] deleteObjectStore method and updates to IDBDatabase.objectStoreNames on the client

2011-06-10 Thread Eliot Graff
May these updates: Updated the IDBDatabase.deleteObjectStore method to return void. For IDBDatabase.deleteObjectStore and IDBDatabase.createObjectStore added a sentence to the description to say: This method will synchronously modify the IDBDatabase.objectStoreNames property.

RE: [IndexedDB] deleteObjectStore method and updates to IDBDatabase.objectStoreNames on the client

2011-05-04 Thread Israel Hilerio
The reason I was thinking that deleteObjectStore was async was because it returns an IDBRequest interface and the pattern implies that the onsuccess handler needs to be called for me to be sure that the operation happened successfully. Regarding the createObjectStore, it returns immediately

Re: [IndexedDB] deleteObjectStore method and updates to IDBDatabase.objectStoreNames on the client

2011-05-04 Thread Jeremy Orlow
On Wed, May 4, 2011 at 9:40 PM, Israel Hilerio isra...@microsoft.comwrote: The reason I was thinking that deleteObjectStore was async was because it returns an IDBRequest interface and the pattern implies that the onsuccess handler needs to be called for me to be sure that the operation

Re: [IndexedDB] deleteObjectStore method and updates to IDBDatabase.objectStoreNames on the client

2011-05-04 Thread Jonas Sicking
On Wed, May 4, 2011 at 9:49 AM, Jeremy Orlow jor...@chromium.org wrote: On Wed, May 4, 2011 at 9:40 PM, Israel Hilerio isra...@microsoft.com wrote: The reason I was thinking that deleteObjectStore was async was because it returns an IDBRequest interface and the pattern implies that the

[IndexedDB] deleteObjectStore method and updates to IDBDatabase.objectStoreNames on the client

2011-05-03 Thread Israel Hilerio
In looking at createObjectStore on IDBDatabase, it seems that we would have to update the IDBDatabase.objectStoreNames attribute on the client side after returning the IDBObjectStore. Otherwise, it would be difficult to detect that an objectStore with the same name already exists and throw a