Description
Consider the following scenario executed from JDBC/ODBC driver:
1) Open transaction
2) Get a cursor for some large SELECT
3) Close transaction
4) Overwrite some of not-yet-returned values for the cursor
5) Force vacuum
6) Read remaining values from the cursor
Will we get correct result? Most probably no, because we close transaction on commit without consulting to any opened cursors.
Possible solutions:
1) Extend transaction lifetime until all cursors are closed
2) Or close the cursors forcibly and throw proper error message
Attachments
Issue Links
- relates to
-
IGNITE-9410 Add transactions support to thin clients
-
- Resolved
-