[
https://issues.apache.org/jira/browse/IGNITE-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-21002:
--------------------------------------
Description:
We need to add documentation about the ability to execute SQL scripts.
One thing to remember to mention is that if the user leaves an open transaction
initiated by the script, it will be rolled back after the script completes
execution.
For example:
{code:sql}
CREATE TABLE TEST(ID INT);
START TRANSACTION;
INSERT INTO TEST(1);
{code}
Since the transaction remains open, all changes made within it will be undone
when the script completes.
Another thing is that {{COMMIT}} does nothing without an open script
transaction.
{code:sql}
CREATE TABLE TEST(ID INT);
COMMIT;
COMMIT;
{code}
Script must be executed without errors.
TBD: describe jdbc script-tx integration restrictions.
TX control statements do not supported in non autocommit mode (see
IGNITE-21020).
was:
We need to add documentation about the ability to execute SQL scripts.
One thing to remember to mention is that if the user leaves an open transaction
initiated by the script, it will be rolled back after the script completes
execution.
For example:
{code:sql}
CREATE TABLE TEST(ID INT);
START TRANSACTION;
INSERT INTO TEST(1);
{code}
Since the transaction remains open, all changes made within it will be undone
when the script completes.
Another thing is that {{COMMIT}} does nothing without an open script
transaction.
{code:sql}
CREATE TABLE TEST(ID INT);
COMMIT;
COMMIT;
{code}
Script must be executed without errors.
TBD: describe jdbc script-tx integration restrictions.
> Document the ability to execute SQL multi-statement queries.
> ------------------------------------------------------------
>
> Key: IGNITE-21002
> URL: https://issues.apache.org/jira/browse/IGNITE-21002
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> We need to add documentation about the ability to execute SQL scripts.
> One thing to remember to mention is that if the user leaves an open
> transaction initiated by the script, it will be rolled back after the script
> completes execution.
> For example:
> {code:sql}
> CREATE TABLE TEST(ID INT);
> START TRANSACTION;
> INSERT INTO TEST(1);
> {code}
> Since the transaction remains open, all changes made within it will be undone
> when the script completes.
> Another thing is that {{COMMIT}} does nothing without an open script
> transaction.
> {code:sql}
> CREATE TABLE TEST(ID INT);
> COMMIT;
> COMMIT;
> {code}
> Script must be executed without errors.
> TBD: describe jdbc script-tx integration restrictions.
> TX control statements do not supported in non autocommit mode (see
> IGNITE-21020).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
