Re: [Bug 11398] New: [IndexedDB] Methods that take multiple optional parameters should instead take an options object

On Tue, Dec 14, 2010 at 8:47 AM, Jeremy Orlow <jorlow@chromium.org> wrote:

> Btw, I forgot to mention IDBDatabase.transaction which I definitely think
> should take an options object as well.


Hmm.. I think we should make the first argument required, I actually thought
it was until I looked just now. I don't see what the use case is for opening
all tables. In fact, it seems rather harmful that the syntax which will
result in more lock contention is simpler than the syntax which is better
optimized.

This leaves two optional arguments, the second of which is likely very
rarely going to be used. In fact, I wouldn't mind removing it entirely since
it just seems like it risks causing race conditions. And it's technically
syntax sugar since you can always use setTimeout and call .abort() manually.

/ Jonas