« Changelog History


ArangoDB v1.4.1-rc1 Release Notes

Release Date: 2013-11-07 // almost 12 years ago

    • 🛠 fixed issue #635: Web-Interface should have a "Databases" Menu for Management

    • 🛠 fixed issue #624: Web-Interface is missing a Database selector

    • 🛠 fixed segfault in bitarray query

    • 🛠 fixed issue #656: Cannot create unique index through web interface

    • 🛠 fixed issue #654: bitarray index makes server down

    • 🛠 fixed issue #653: Slow query

    • 🛠 fixed issue #650: Randomness of any() should be improved

    • made AQL DOCUMENT() function polymorphic and work with just one parameter.

    This allows using the DOCUMENT function like this:

      DOCUMENT('users/john')
  DOCUMENT([ 'users/john', 'users/amy' ])

    in addition to the existing use cases:

      DOCUMENT(users, 'users/john')
  DOCUMENT(users, 'john')
  DOCUMENT(users, [ 'users/john' ])
  DOCUMENT(users, [ 'users/john', 'users/amy' ])
  DOCUMENT(users, [ 'john', 'amy' ])
    • simplified usage of ArangoDB batch API

    It is not necessary anymore to send the batch boundary in the HTTP Content-Type header. Previously, the batch API expected the client to send a Content-Type header ofmultipart/form-data; boundary=<some boundary value>. This is still supported in ArangoDB 2.0, but clients can now also omit this header. If the header is not present in a client request, ArangoDB will ignore the request content type and read the MIME boundary from the beginning of the request body.

    This also allows using the batch API with the Swagger "Try it out" feature (which is not too good at sending a different or even dynamic content-type request header).

    • ➕ added API method GET /_api/database/user

    This returns the list of databases a specific user can see without changing the username/passwd.

    • 📚 issue #424: Documentation about IDs needs to be upgraded