You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG
+8-4Lines changed: 8 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Release notes for the ArangoDB-PHP driver 3.0.9
1
+
Release notes for the ArangoDB-PHP driver 3.0.x
2
2
===============================================
3
3
4
4
This version of the driver is compatible with ArangoDB 3.0.x
@@ -9,14 +9,18 @@ Please use ones of the `2.x` branches of the driver for 2.x-compatibility.
9
9
10
10
Caution!!!
11
11
12
-
There are still deprecated functions in the code, which should have been removed in the 2.x series of the driver.
13
-
These will now be removed with the 3.1 version of the driver, in order to clean up the codebase. Please check and change your code accordingly.
12
+
There are still deprecated functions in the code, which should have been removed in the first 3.0 version of the driver, however, we missed this opportunity.
13
+
These will now finally be removed with the 3.1 version of the driver, in order to clean up the codebase. Please check and change your code accordingly.
14
14
All deprecated functions can now also be found in the docs inside the "Deprecated" view.
15
15
16
16
Changes
17
17
=======
18
18
19
-
- This version is mainly a cleanup of code in order to produce a nicer documentation for the driver.
19
+
- GraphHandler: Optimized code to do less work when not necessary
20
+
- GraphHandler: Implemented optional cache that caches the Vertex/Edge-Collections instead of making expensive calls to the DB.
21
+
- GraphHandler: Is now batch-able. However, if any collections need to be fetched, they will be done out-of-batch.
22
+
If a lot of calls to the GraphHandler are being made, the use of the new caching functionality is encouraged.
23
+
- Batches: Some work has been done, to optimize batches. This is still in development.
@@ -396,64 +409,66 @@ public function splitWithContentIdKey($pattern, $string)
396
409
}
397
410
398
411
399
-
/**
400
-
* Processes this batch. This sends the captured requests to the server as one batch.
401
-
*
402
-
* @throws ClientException
403
-
* @return HttpResponse|Batch - Batch if processing of the batch was successful or the HttpResponse object in case of a failure. A successful process just means that tha parts were processed. Each part has it's own response though and should be checked on its own.
404
-
*/
405
-
publicfunctionprocess()
406
-
{
407
-
$this->stopCapture();
408
-
$this->setBatchRequest(true);
409
-
$data = '';
410
-
$batchParts = $this->getBatchParts();
411
-
412
-
if (count($batchParts) === 0) {
413
-
thrownewClientException('Can\'t process empty batch.');
* Processes this batch. This sends the captured requests to the server as one batch.
414
+
*
415
+
* @return HttpResponse|Batch - Batch if processing of the batch was successful or the HttpResponse object in case of a failure. A successful process just means that tha parts were processed. Each part has it's own response though and should be checked on its own.
416
+
*
417
+
* @throws ClientException
418
+
* @throws \triagens\ArangoDb\Exception
419
+
*/
420
+
publicfunctionprocess()
421
+
{
422
+
$this->stopCapture();
423
+
$this->setBatchRequest(true);
424
+
$data = '';
425
+
$batchParts = $this->getBatchParts();
426
+
427
+
if (count($batchParts) === 0) {
428
+
thrownewClientException('Can\'t process empty batch.');
0 commit comments