Add documentation for OQL UPDATE statement for attributes

Author: dahfjkg

content/en/docs/refguide/modeling/domain-model/oql/oql-delete-statement.md

@@ -0,0 +1,118 @@
+---
+title: "OQL Statements"
+url: /refguide/oql-statements/
+beta: true
+weight: 210
+aliases:
+    - /refguide/oql-delete-statement/
+---
+
+{{% alert color="warning" %}} This feature is experimental. For more information, see [Release Status](/releasenotes/release-status/). {{% /alert %}}
+
+## Introduction
+
+From Mendix version 11.1, you can delete objects in bulk using OQL `DELETE` statements. From Mendix version 11.3, it is also possible to update object attributes in bulk using OQL `UPDATE` statements.
+
+OQL statements are translated to SQL statements that are sent to the database.
+This can be much faster than retrieving the objects in a microflow and then updating or deleting the resulting list.
+
+This feature is experimental and currently only accessible through the Java API by writing a Java action.
+
+## Java API for OQL updates
+
+OQL Statements can be executed using the `Core.createOqlStatement` Java API. For example:
+
+```java
+Core.createOqlStatement("DELETE FROM Module.Customer WHERE Name = 'Mary'").execute(context) 
+```
+
+You can pass values as parameters to the query. For example:
+
+```java
+Core.createOqlStatement("DELETE FROM Module.Customer WHERE Name = $nameParam")
+    .setVariable("nameParam", customerName)
+    .execute(context)
+```
+
+The `execute()` method returns the number of objects that were affected by the statement.
+
+## `DELETE` Statement {#oql-delete}
+
+The syntax of `DELETE` statements is:
+
+```sql
+DELETE FROM <entity> WHERE <condition>
+```
+
+`condition` can be anything that can appear in an OQL [WHERE clause](/refguide/oql-clauses/#where).
+
+### OQL `DELETE` Limitations
+
+* You cannot use OQL `DELETE` with entities that have associations with non-default delete behavior. These are associations that use either "Delete as well" or "Delete only if not associated".
+* You cannot use OQL DELETE to delete objects of type `System.FileDocument` or any specialization of it.
+* General [limitations](#oql-limitations) for OQL statements apply.
+
+## `UPDATE` Statement {#oql-update}
+
+The syntax of `UPDATE` statements is:
+
+```sql
+UPDATE <entity>
+SET { <attribute> = <expression> } [ ,...n ]
+WHERE <condition>
+```
+
+`entity` is the entity whose objects are being updated.
+
+`attribute` is an attribute of the entity that is being updated. Multiple attributes can be updated in the same statement.
+
+`expression` is a new value of an attribute. Any [OQL expression](/refguide/oql-expressions) is allowed. The value type of the expression should match the attribute type according to [type coercion precedence](/refguide/oql-expression-syntax/#type-coercion).
+
+`condition` can be anything that can appear in an OQL [WHERE clause](/refguide/oql-clauses/#where).
+
+Example:
+
+```sql
+UPDATE
+    Module.Customer
+SET
+    TotalAmount = (
+        SELECT SUM(Amount)
+        FROM Module.Order
+        WHERE Module.Order_Customer/Module.Customer/ID = Module.Customer/ID
+    ),
+    Location = Module.Customer_Address/Module.Address/City,
+    
+
+```
+
+### OQL `UPDATE` Limitations
+
+* At the moment, it is only possible to update attributes, not associations.
+* If a subquery or a long path over a many-to-one or many-to-many association is used as `expression`, it can result in muptile values. In that case, a database-level exception will occur when running the statement.
+* In case of inheritance, all attributes should belong to the same inheritance level. It is not possible to update attributes of a generalization and a specialization in the same statement.
+* General [limitations](#oql-limitations) for OQL statements apply.
+
+## Joins
+
+You cannot directly join other entities in the `FROM` clause of OQL `DELETE` or in the `UPDATE` clause of OQL `UPDATE`. However, you can achieve the same result using long paths or subqueries. For example:
+
+```sql
+DELETE FROM Module.Order WHERE Module.Order_Customer/Module.Customer/Name = 'Mary'
+```
+
+or
+
+```sql
+UPDATE Module.Order SET CustomerName = 'Mary' WHERE ID IN
+  ( SELECT ID FROM Module.Order
+    INNER JOIN Module.Customer ON Module.Customer/CustomerID = Module.Order/CustomerID
+    WHERE Module.Customer/Name = 'Mary' )
+```
+
+## General limitations for OQL statements {#oql-limitations}
+
+* OQL statements can be used only with persitable entities.
+* Entity access rules are not applied to any OQL statements.
+* No event handlers will be executed.
+* Runtime and client state will not be updated with the changes.

content/en/docs/refguide/modeling/domain-model/oql/oql-statements.md

@@ -14,7 +14,7 @@ weight: 99
 ### New Features
 
 * We added a new, experimental [Runtime API](/apidocs-mxsdk/apidocs/runtime-api-11/) call, `Core.createOqlStatement`, to execute OQL statements.
-* We implemented [OQL DELETE](/refguide/oql-delete-statement/) statements to delete objects in bulk directly in the database without having to instantiate them in the runtime. This feature is available only in Java API.
+* We implemented [OQL DELETE](/refguide/oql-statements/#oql-delete) statements to delete objects in bulk directly in the database without having to instantiate them in the runtime. This feature is available only in Java API.
 * You can now add a query parameter at any request in the Consumed REST Service document through the Query Parameters grid or through the URL editor.
 * We added support for uploading images and PDF files for your requests in [Maia for Domain Model](/refguide/maia-for-domain-model/).
 * We added support for access keys in context menus. The following editors are supported: domain model, microflow, page, mapping, and workflow.