mirror of https://gitee.com/bigwinds/arangodb
updated CHANGELOG
This commit is contained in:
parent
7a732f6c68
commit
15c20ad4ec
|
@ -5,6 +5,12 @@ v1.2.alpha (XXXX-XX-XX)
|
|||
Javascript and REST API
|
||||
|
||||
* make server stop after upgrade procedure when invoked with `--upgrade option`.
|
||||
When started with the `--upgrade` option, the server will perfom
|
||||
the upgrade, and then exit with a status code indicating the result of the
|
||||
upgrade (0 = success, 1 = failure). To start the server regularly in either
|
||||
daemon or console mode, the `--upgrade` option must not be specified.
|
||||
This change was introduced to allow init.d scripts check the result of
|
||||
the upgrade procedure, even in case an upgrade was successful.
|
||||
this was introduced as part of issue #391.
|
||||
|
||||
* added AQL function EDGES()
|
||||
|
|
|
@ -99,6 +99,17 @@ All collection datafiles will be backed up in the original collection
|
|||
directories in the database directory. You can easily detect the backup
|
||||
files because they have a file ending of `.old`.
|
||||
|
||||
Please note that the upgrade behavior in 1.2 was slightly changed compared
|
||||
to 1.1:
|
||||
- in 1.1, when starting `arangod` with `--upgrade`, the server performed the
|
||||
upgrade, and if the upgrade was successfully, continued to work in either
|
||||
daemon or console mode.
|
||||
- in 1.2, when started with the `--upgrade` option, the server will perfom
|
||||
the upgrade, and then exit with a status code indicating the result of the
|
||||
upgrade (0 = success, 1 = failure). To start the server regularly in either
|
||||
daemon or console mode, the `--upgrade` option must not be specified.
|
||||
This change was introduced to allow init.d scripts check the result of
|
||||
the upgrade procedure, even in case an upgrade was successful.
|
||||
|
||||
Troubleshooting{#Upgrading12Troubleshooting}
|
||||
============================================
|
||||
|
|
Loading…
Reference in New Issue