Merge pull request #280 from gramian/main

Comparison between SQL and SQLscript

src/main/asciidoc/sql/SQL-Script.adoc

@@ -3,11 +3,18 @@
 
 image:../images/edit.png[link="https://github.com/ArcadeData/arcadedb-docs/blob/main/src/main/asciidoc/sql/SQL-Script.adoc" float=right]
 
-ArcadeDB allows execution of arbitrary scripts written in Javascript or any scripting language installed in the JVM. ArcadeDB supports a minimal SQL engine to allow a batch of commands.
+ArcadeDB allows execution of arbitrary scripts written in Javascript or any scripting language installed in the JVM.
 
-Batch of commands are very useful when you have to execute multiple things at the server side avoiding the network roundtrip for each command.
+ArcadeDB supports a minimal SQL engine to allow a batch of commands, called "SQL Script" (`sqlscript`).
+Batches of commands are useful when you have to execute multiple things at the server side and avoiding the network roundtrip for each command.
 
-SQL Batch supports all the ArcadeDB <<SQL-Commands,SQL Commands>>, plus the following:
+The following list highlights the differences between `sql` and `sqlscript`:
+
+* `sqlscript` allows multiple statements, `sql` is limited to a single statement.
+* A `sqlscript` batch is automatically transaction, a `sql` query or command by itself is not.
+* `sqlscript` supports additional control flow constructs (i.e. loops and conditionals, see below).
+
+SQL Script supports all the ArcadeDB <<SQL-Commands,SQL Commands>>, plus the following:
 
 * `BEGIN [isolation &lt;isolation-level&gt;]`, where `&lt;isolation-level&gt;` can be `READ_COMMITTED`, `REPEATABLE_READ`. By default is `READ_COMMITTED`
 * `COMMIT [retry &lt;retry&gt;]`, where: