Incompatible changes in ArangoDB 3.6

The following incompatible changes have been made in ArangoDB 3.6:

ArangoDB 3.6 enforces valid date ranges for working with date/time in AQL. The valid date ranges for any AQL date/time function are:

• for string date/time values: (including) up to "9999-12-31T23:59:59.999Z" (including)

Any date/time operations that produce date/time outside the valid ranges stated above will make the function return null and trigger a warning too. Example:

The following startup options have been removed in ArangoDB 3.6:

• : this option was used in previous versions to control the maximum size (in bytes) of VelocyPack chunks when using the VelocyStream (VST) protocol. This is now handled automatically by the server and does not need any configuration.

We recommend to switch to RocksDB even before the removal of MMFiles. RocksDB is the default storage engine since v3.4.0.

Introduced in: v3.6.5