This is an automated email from the ASF dual-hosted git repository.

amashenkov pushed a commit to branch ignite-22681
in repository https://gitbox.apache.org/repos/asf/ignite-3.git

commit 408a4c688739332e8cb06cbf3a3cb1f65cbf25f4
Author: amashenkov <[email protected]>
AuthorDate: Tue Aug 6 15:35:32 2024 +0300

    Actualize SQL error codes in documentation
---
 .../administrators-guide/handling-exceptions.adoc  | 22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)

diff --git a/docs/_docs/administrators-guide/handling-exceptions.adoc 
b/docs/_docs/administrators-guide/handling-exceptions.adoc
index 3a9a65479e..937ddbdb74 100644
--- a/docs/_docs/administrators-guide/handling-exceptions.adoc
+++ b/docs/_docs/administrators-guide/handling-exceptions.adoc
@@ -73,19 +73,15 @@ When the exception happens, Ignite 3 provides a UUID of the 
specific exception,
 |===
 |Exception     |Description
 
-|`IGN-SQL-1`|Failed to read a page after last existing one.
-|`IGN-SQL-2`|Failed to read response from a query that does not return rows.
-|`IGN-SQL-3`|Schema not found error.
-|`IGN-SQL-4`|Cursor is already closed error.
-|`IGN-SQL-5`|Statement parsing error. SQL string is not grammatically valid.
-|`IGN-SQL-6`|Statement validation error.SQL string is not semantically valid 
or contains prohibited operations.
-|`IGN-SQL-7`|Constraint violation error, for example, primary key violation.
-|`IGN-SQL-8`|Statement got cancelled.
-|`IGN-SQL-9`|Runtime error. Usually caused an SQL error, for example numeric 
overflow.
-|`IGN-SQL-10`|Planning timed out without finding any valid plan.
-|`IGN-SQL-11`|Operation got rejected because SQL session was closed.
-|`IGN-SQL-12`|SQL engine was unable to map query on current cluster topology. 
Most likely, the partition or view is not available because all nodes 
containing it are offline.
-|`IGN-SQL-13`|Execution of transaction control statement inside an external 
transaction is forbidden.
+|`IGN-SQL-1`|Failed to read response from a query that does not return rows.
+|`IGN-SQL-2`|Schema not found error.
+|`IGN-SQL-3`|Statement parsing error. SQL string is not grammatically valid.
+|`IGN-SQL-4`|Statement validation error.SQL string is not semantically valid 
or contains prohibited operations.
+|`IGN-SQL-5`|Constraint violation error, for example, primary key violation.
+|`IGN-SQL-6`|Statement got cancelled.
+|`IGN-SQL-7`|Runtime error. Usually caused an SQL error, for example numeric 
overflow.
+|`IGN-SQL-8`|SQL engine was unable to map query on current cluster topology. 
Most likely, the partition or view is not available because all nodes 
containing it are offline.
+|`IGN-SQL-9`|Execution of transaction control statement inside an external 
transaction is forbidden.
 |===
 
 == Meta Storage Exceptions

Reply via email to