History

Jan db7fcdce7a don't run compact() on a collection after a truncate() was done in the same transaction (#8471 ) running compact() in the same transaction will only increase the data size on disk due to RocksDB not being able to remove any documents physically due to the snapshot that is taken at transaction start. This change also exposes db.<collection>.compact() in the arangosh, in order to manually run a compaction on the data range of a collection should it be needed for maintenance.		2019-03-20 17:44:06 +01:00
..
Deprecated	…
JavaScriptModules	fix failing non-deterministic query-stream test (#7296 )	2018-11-13 11:37:09 +01:00
References	don't run compact() on a collection after a truncate() was done in the same transaction (#8471 )	2019-03-20 17:44:06 +01:00
ErrorCodes.md	…
Glossary.md	Doc - _rev warning (#8204 )	2019-02-21 23:37:14 +01:00
README.md	…

Appendix

References: Brief overviews over interfaces and objects
- db: the db object
- collection: the collection object
- cursor: the cursor object
JavaScript Modules: List of built-in and supported JS modules
Deprecated: Features that are considered obsolete and may get removed eventually
Error codes and meanings: List of all possible errors that can be encountered
Glossary: Disambiguation page