diff --git a/Documentation/Books/Users/Databases/Notes.mdpp b/Documentation/Books/Users/Databases/Notes.mdpp index cbaf967283..9f89da9f3c 100644 --- a/Documentation/Books/Users/Databases/Notes.mdpp +++ b/Documentation/Books/Users/Databases/Notes.mdpp @@ -1,7 +1,8 @@ !CHAPTER Notes about Databases Please keep in mind that each database contains its own system collections, -which need to set up when a database is created. This will make the creation of a database take a while. +which need to be set up when a database is created. This will make the creation +of a database take a while. Replication is configured on a per-database level, meaning that any replication logging or applying for a new database must be configured explicitly after a new database has been created. diff --git a/Documentation/Books/Users/Databases/README.mdpp b/Documentation/Books/Users/Databases/README.mdpp index b66c60ba00..a47a1d54d7 100644 --- a/Documentation/Books/Users/Databases/README.mdpp +++ b/Documentation/Books/Users/Databases/README.mdpp @@ -3,22 +3,21 @@ This is an introduction to managing databases in ArangoDB from within JavaScript. -While being in an established connection to ArangoDB, the current -database can be changed explicitly by using the *db._useDatabase()* +When you have an established connection to ArangoDB, the current +database can be changed explicitly using the *db._useDatabase()* method. This will switch to the specified database (provided it exists and the user can connect to it). From this point on, any -following actions in the same shell or connection will use the -specified database unless otherwise specified. +following action in the same shell or connection will use the +specified database, unless otherwise specified. *Note*: If the database is changed, client drivers need to store the current database name on their side, too. This is because connections in ArangoDB do not contain any state information. All state information is contained in the HTTP request/response data. -Connecting to a specific database from arangosh is possible with -the above command after arangosh has been started, but it is also -possible to specify a database name when invoking arangosh. -For this purpose, use the command-line parameter *--server.database*, +To connect to a specific database after arangosh has started use the command +described above. It is also possible to specify a database name when invoking +arangosh. For this purpose, use the command-line parameter *--server.database*, e.g. > arangosh --server.database test @@ -28,3 +27,4 @@ access multiple databases, even if they exist. The only intended and supported way in ArangoDB is to use one database at a time for a command, an action, a script or a query. Operations started in one database must not switch the database later and continue operating in another. + diff --git a/Documentation/Books/Users/FirstSteps/README.mdpp b/Documentation/Books/Users/FirstSteps/README.mdpp index 43493fe042..c690376056 100644 --- a/Documentation/Books/Users/FirstSteps/README.mdpp +++ b/Documentation/Books/Users/FirstSteps/README.mdpp @@ -45,12 +45,12 @@ For more in-depth information: The ArangoDB package comes with the following programs: * _arangod_: The ArangoDB database daemon. This server program is - intended to run as daemon process and to server the various clients + intended to run as a daemon process and to serve the various clients connection to the server via TCP / HTTP. See [Details about the ArangoDB Server](../FirstSteps/Arangod.md) * _arangosh_: The ArangoDB shell. A client that implements a read-eval-print loop (REPL) and provides functions to access and administrate the ArangoDB server. See [Details about the ArangoDB Shell](../FirstSteps/Arangosh.md). -* _arangoimp_: A bulk importer for the ArangoDB server +* _arangoimp_: A bulk importer for the ArangoDB server. See [Details about Arangoimp](../Arangoimp/README.md). * _arangodump_: A tool to create backups of an ArangoDB database. See [Details about Arangodump](../Arangodump/README.md).