Maximilian Gärber

👍

Since BaseX usage can not (and maybe better should not) predicted (lib vs tool vs dbms...), I propose adding hooks or annotations so it would be possible to introduce such...

1. Since resource/document is the unit of storage, this would be a natural fit for triggers 2. See above, path of document 3. XQuery expressions or functions would be really...

+1 for the current outcome of the discussion. While re-reading some SQL trigger spec, I think we need to clarify what the "ON " part really means. In SQL terms...

It might be enough to let the db client declare the org.basex.core.Context. Example code: https://github.com/axxepta/basex-multitenant/blob/master/src/main/java/de/axxepta/basex/App.java The main question is if there are any side effects to switch the Context from...

Since it came up in this thread: xqerl and couchdb via RPC https://gist.github.com/zadean/1f75901f09a2aa2ba482a2ced00b2a63

I tend to APIs with lighter footprint (jQuery in this case). On the other hand, the only _official_ spec is A+ (also ECMA6) and I just read on the jQuery...

Now having said that - A+ is only defining `then` semantics. Q just added everything else on its own. So apart from `then` there is no single source of truth...

So, ECMA defines more methods, as always [Mozilla MDN on Promise](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Promise) is a good read. `Promise.all() Promise.prototype.catch() Promise.prototype.then() Promise.race() Promise.reject() Promise.resolve()` Offical ECMA 2016 Spec: https://tc39.github.io/ecma262/#sec-promise-objects

I'll soon add it to a project I am working on (for async image processing etc.) and tell you about my progress (or even add you to the repo)