Apr 24th 2019
Listener events are usually sent as soon as a transaction is committed, but before the change is visible to queries. Listeners can now prefer receiving events after they have been made visible instead, by specifying
visibility=query. See the listener API reference for more details.
The query execution plan, useful to advanced users when optimizing slow queries, can now be retrieved by specifying
explain=true for queries. This will return the plan as plain text in the
explain field of the result. The actual query exection can be skipped by specifying
We have also been working on lots of infrastructure improvements that lay the foundation for upcoming features and improved scalability - stay tuned.
Other improvements include:
matchare no longer considered reserved keywords, and can be used as attribute names.
identity()were added, and are recommended over the default query parameters
$identitywhich are deprecated.
*[_id == "id"].authors.name) sometimes returned