Merge branch 'main' of https://github.com/arangodb/docs-hugo into aql-timezone

Author: Simran-B

README.md

@@ -778,7 +778,7 @@ Netlify supports server-side redirects configured with a text file
 This is helpful when renaming folders with many subfolders and files because
 there is support for splatting and placeholders (but not regular expressions). See
 [Redirect options](https://docs.netlify.com/routing/redirects/redirect-options/)
-for details. The configuration file is `site/content/_redirects`.
+for details. The configuration file is `site/static/_redirects`.
 
 Otherwise, the following steps are necessary for moving content:
 1. Rename file or folder

site/config/_default/config.yaml

@@ -16,6 +16,9 @@ module:
     - source: "content/images"
       target: "assets/images"
 
+    - source: "static"
+      target: "static"
+
 markup:
   highlight:
     noClasses: false

site/content/3.11/develop/http-api/queries/aql-queries.md

@@ -178,9 +178,9 @@ Content-type: application/json
 }
 ```
 
-If the `allowRetry` query option is set to `true`, then the response object
-contains a `nextBatchId` attribute, except for the last batch (if `hasMore` is
-`false`). If retrieving a result batch fails because of a connection issue, you
+The response object contains a `nextBatchId` attribute, except for the last batch
+(when `hasMore` is `false`). If the `allowRetry` query option is set to `true`
+and if retrieving a result batch fails because of a connection issue, you
 can ask for that batch again using the `POST /_api/cursor/<cursor-id>/<batch-id>`
 endpoint. The first batch has an ID of `1` and the value is incremented by 1
 with every batch. Every result response except the last one also includes a

site/content/3.12/aql/high-level-operations/upsert.md

@@ -243,6 +243,20 @@ UPSERT { a: 1234 }
   OPTIONS { indexHint: … , forceIndexHint: true }
 ```
 
+### `readOwnWrites`
+
+The `readOwnWrites` option allows an `UPSERT` operation to process its inputs one
+by one. The default value is `true`. When enabled, the `UPSERT` operation can
+observe its own writes and can handle modifying the same target document multiple
+times in the same query.
+
+When the option is set to `false`, an `UPSERT` operation processes its inputs
+in batches. Normally, a batch has 1000 inputs, which can lead to a faster execution.
+However, when using batches, the `UPSERT` operation can essentially not observe its own writes.
+You should only set the `readOwnWrites` option to `false` if you can
+guarantee that the input of the `UPSERT` leads to disjoint documents being
+inserted, updated, or replaced.
+
 ## Returning documents
 
 `UPSERT` statements can optionally return data. To do so, they need to be followed

site/content/3.12/develop/http-api/queries/aql-queries.md

@@ -178,9 +178,9 @@ Content-type: application/json
 }
 ```
 
-If the `allowRetry` query option is set to `true`, then the response object
-contains a `nextBatchId` attribute, except for the last batch (if `hasMore` is
-`false`). If retrieving a result batch fails because of a connection issue, you
+The response object contains a `nextBatchId` attribute, except for the last batch
+(when `hasMore` is `false`). If the `allowRetry` query option is set to `true`
+and if retrieving a result batch fails because of a connection issue, you
 can ask for that batch again using the `POST /_api/cursor/<cursor-id>/<batch-id>`
 endpoint. The first batch has an ID of `1` and the value is incremented by 1
 with every batch. Every result response except the last one also includes a

site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md

@@ -175,6 +175,21 @@ UPDATE { logins: OLD.logins + 1 } IN users
 
 Read more about [`UPSERT` operations](../../aql/high-level-operations/upsert.md) in AQL.
 
+### `readOwnWrites` option for `UPSERT` operations
+
+A `readOwnWrites` option has been added for `UPSERT` operations. The default
+value is `true` and the behavior is identical to previous versions of ArangoDB that
+do not have this option. When enabled, an `UPSERT` operation processes its
+inputs one by one. This way, the operation can observe its own writes and can
+handle modifying the same target document multiple times in the same query.
+
+When the option is set to `false`, an `UPSERT` operation processes its inputs
+in batches. Normally, a batch has 1000 inputs, which can lead to a faster execution.
+However, when using batches, the `UPSERT` operation cannot observe its own writes.
+Therefore, you should only set the `readOwnWrites` option to `false` if you can
+guarantee that the input of the `UPSERT` leads to disjoint documents being
+inserted, updated, or replaced.
+
 ### Added AQL functions
 
 The new `PARSE_COLLECTION()` and `PARSE_KEY()` let you more extract the
@@ -225,6 +240,13 @@ timezone, and the second date in the second timezone:
 
 See [Date functions in AQL](../../aql/functions/date.md#date_dayofweek)
 
+### Improved `move-filters-into-enumerate` optimizer rule
+
+The `move-filters-into-enumerate` optimizer rule can now also move filters into
+`EnumerateListNodes` for early pruning. This can significantly improve the
+performance of queries that do a lot of filtering on longer lists of
+non-collection data.
+
 ## Indexing
 
 ### Stored values can contain the `_id` attribute