The IndexedDB API uses the strange pattern to define callbacks after the open (and I think the transaction) call and seems to rely on the browser to first assign the callbacks and then really run the open call (related question).

Now this is troubling, when I'd like to put some code in the browser developer console to query the database, especially when I want to run two queries after each other, which then seem to have a race condition. I already had before problems with error messages about already closed transactions and so on.

Is there a simple way to "just" sequentially run a few queries after each other?