adjusting documentation

Documentation/Books/Drivers/JS/Reference/Database/Transactions.md

@@ -56,16 +56,6 @@ Performs a server-side transaction and returns its return value.
 
     Determines the transaction size limit in bytes. Honored by the RocksDB storage engine only.
 
-  * **intermediateCommitCount**: `number` (optional)
-
-    Determines the maximum number of operations after which an intermediate commit is
-    performed automatically. Honored by the RocksDB storage engine only.
-
-  * **intermediateCommitSize**: `number` (optional)
-
-    Determine the maximum total size of operations after which an intermediate commit is
-    performed automatically. Honored by the RocksDB storage engine only.
-
 If _collections_ is an array or string, it will be treated as
 _collections.write_.
 

Documentation/Books/Manual/Transactions/Limitations.md

@@ -71,7 +71,7 @@ transactional properties of a single server apply (fully ACID).
 With RocksDB storage engine
 ---------------------------
 
-Data of ongoing transactions is stored in RAM. Transactions that get too big 
+Data of ongoing transactions is stored in RAM. Query-Transactions that get too big 
 (in terms of number of operations involved or the total size of data created or
 modified by the transaction) will be committed automatically. Effectively this 
 means that big user transactions are split into multiple smaller RocksDB 
@@ -100,8 +100,8 @@ is committed automatically and a new transaction is started. The value is specif
 If the number of operations in a transaction reaches this value, the transaction is 
 committed automatically and a new transaction is started.
 
-The above values can also be adjusted per transaction, by setting the following
-attributes in the call to *db._executeTransaction()*:
+The above values can also be adjusted per query, by setting the following
+attributes in the call to *db._query()*:
 
 - *maxTransactionSize*: transaction size limit in bytes
 - *intermediateCommitSize*: maximum total size of operations after which an intermediate

Documentation/Books/Manual/Transactions/TransactionInvocation.md

@@ -65,11 +65,6 @@ Additionally, *object* can have the following optional attributes:
 The following attributes can be used for transactions in the RocksDB storage engine:
 
 - *maxTransactionSize*: transaction size limit in bytes
-- *intermediateCommitSize*: maximum total size of operations after which an intermediate
-  commit is performed automatically
-- *intermediateCommitCount*: maximum number of operations after which an intermediate
-  commit is performed automatically
-
 
 Declaration of collections
 --------------------------

Documentation/DocuBlocks/Rest/Transactions/post_api_transaction.md

@@ -42,14 +42,6 @@ optional arguments passed to *action*.
 @RESTBODYPARAM{maxTransactionSize,integer,optional,int64}
 Transaction size limit in bytes. Honored by the RocksDB storage engine only.
 
-@RESTBODYPARAM{intermediateCommitSize,integer,optional,int64}
-Maximum total size of operations after which an intermediate commit is performed 
-automatically. Honored by the RocksDB storage engine only.
-
-@RESTBODYPARAM{intermediateCommitCount,integer,optional,int64}
-Maximum number of operations after which an intermediate commit is performed 
-automatically. Honored by the RocksDB storage engine only.
-
 @RESTDESCRIPTION
 The transaction description must be passed in the body of the POST request.
 

js/server/tests/recovery/intermediate-commit-truncate-rocksdb.js

@@ -43,20 +43,8 @@ function runSetup () {
     c.insert({ _key: 'test' + i, value: i });
   }
 
-  c.truncate({ waitForSync: true });
+  c.truncate({ waitForSync: true, intermediateCommitCount: 1000 });
   internal.debugSegfault('crashing server');
-
-  db._executeTransaction({
-    intermediateCommitCount: 1000,
-    collections: {
-      write: 'UnitTestsRecovery'
-    },
-    action: function () {
-      var db = require('@arangodb').db;
-
-      
-    }
-  });
 }
 
 // //////////////////////////////////////////////////////////////////////////////