Navigation:
ArangoDB for Mac OS X 3.11.0 freeware
Build high performance applications using a convenient SQL-like query language or JavaScript extensions. ArangoDB provides you with and easy to configure database server that features a flexible data model to help you store key-value pairs, graphs and documents. ...
| Author | ArangoDB |
| Released | 2023-10-19 |
| Filesize | 82.80 MB |
| Downloads | 750 |
| OS | Mac OS X |
| Installation | Instal And Uninstall |
| Keywords | database server, run query, database, data model, query, server, graph, configure, algorithm, AOL |
| Users' rating (18 rating) |
ArangoDB for Mac OS X Free Download - we do not host any ArangoDB for Mac OS X torrent files or links of ArangoDB for Mac OS X on rapidshare.com, depositfiles.com, megaupload.com etc. All ArangoDB for Mac OS X download links are direct ArangoDB for Mac OS X download from publisher site or their selected mirrors.
| 3.11.0 | Oct 19, 2023 | New Release | |
| 3.7.10 | Mar 19, 2021 | New Release | Reasonably harden MoveShard against unexpected VelocyPack input. Follower DB servers will now respond with error code `TRI_ERROR_CLUSTER_SHARD_FOLLOWER_REFUSES_OPERATION` to any read request. This fixes inadequate HTTP 404 responses from followers, e.g. during chaos tests. Fixed Github issue #13632: Query Fails on Upsert with Replace_nth. Updated arangosync to 1.2.3. Backported AQL sort performance improvements from devel. This change can improve the performance of local sorts operations, e.g. |
| 3.7.2 | Aug 27, 2020 | New Release | Fixed internal issue #744: LIMIT with only offset and constrained heap optimization will use estimation value for ArangoSearch views. Make UPSERT statement with collection bind parameter behave identical to its non-bind parameter counterpart. For example, the query FOR d IN ["key_1", "key_2", "key_3", "key_1"] UPSERT d INSERT d UPDATE d IN @@collection would fail with "unique constraint violation" when used with a collection bind parameter, but the equivalent query FOR d IN ["key_1", "key_2", "key_3", "key_1"] UPSERT d INSERT d UPDATE d IN collectionName with a hard-coded collection name would succeed. This is now fixed so both queries have the same behavior (no failure) in single server. Updated arangosync to 0.7.10. Fixed internal issue #742: Add tick storage in index meta payload for ArangoSearch view links after collection truncate operation. Fixed issue #12304: insert in transaction causing com.arangodb.ArangoDBException: Response: 500, Error: 4 - Builder value not yet sealed. |
