[
https://issues.apache.org/jira/browse/IGNITE-21133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-21133:
----------------------------------------
Description:
For example we already have some results in table and further execution:
{noformat}
1. stmt.execute("START TRANSACTION; INSERT INTO TEST_TX VALUES (1, 1,
'1'); COMMIT"); <- pk violation
2. stmt.execute("SELECT COUNT(*) FROM TEST_TX");
{noformat}
need to lead exception raised on 1 execution but due to closing all unfetched
cursors happens only in 2 execution call, exception will raised there but
expected exception need to be raised from 1.
was:
For example we already have some results in table and further execution:
{noformat}
1. stmt.execute("START TRANSACTION; INSERT INTO TEST_TX VALUES (1, 1,
'1'); COMMIT"); <- pk violation
2. stmt.execute("SELECT COUNT(*) FROM TEST_TX");
{noformat}
need to lead exception raised on 1 execution but due to closing all unfetched
cursors happens only in 2 execution call exception will raised there but
expected exception raised from 1.
> Sql. Closing all dependent statement cursors leads to unexpected exception.
> ---------------------------------------------------------------------------
>
> Key: IGNITE-21133
> URL: https://issues.apache.org/jira/browse/IGNITE-21133
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3
>
> For example we already have some results in table and further execution:
> {noformat}
> 1. stmt.execute("START TRANSACTION; INSERT INTO TEST_TX VALUES (1, 1,
> '1'); COMMIT"); <- pk violation
> 2. stmt.execute("SELECT COUNT(*) FROM TEST_TX");
> {noformat}
> need to lead exception raised on 1 execution but due to closing all unfetched
> cursors happens only in 2 execution call, exception will raised there but
> expected exception need to be raised from 1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
