You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As isql uses two transactions, it is not possible to execute ALTER SESSION RESET. Doing so results in the following error:
D:\DevSoft\FB_tests\Firebird-4.0.0.2133-0_x64>isql -user sysdba -password masterkey localhost:employee
Database: localhost:employee, User: SYSDBA
SQL> alter session reset;
Statement failed, SQLSTATE = 01002
Cannot reset user session
-There are open transactions (2 active)
SQL>
Given the requirement that there is no active transaction (or only the current transaction executing ALTER SESSION RESET), it looks like ISQL needs to get special treatment for handling ALTER SESSION RESET, for example on detection of ALTER SESSION RESET, commit both transaction, or something similar.
The text was updated successfully, but these errors were encountered:
Re-read discussion in fb-devel "[Firebird-devel] ALTER SESSION RESET not allowed if there are transactions?" started by you at 2 jun 2018
where you explicitly agrees with implementation (see last two messages).
Well, to be honest, I had forgotten about that discussion, and reading it back my primary focus in that discussion was on the behaviour for Jaybird and drivers, and not isql.
When I was trying out something in isql yesterday, I was quite surprised by the error when executing ALTER SESSION RESET. I think using SET AUTODDL OFF is not a solution/workaround that is immediately obvious. At minimum it I think it needs to be explicitly mentioned in section ALTER SESSION RESET of the release notes.
Submitted by: @mrotteveel
As isql uses two transactions, it is not possible to execute ALTER SESSION RESET. Doing so results in the following error:
D:\DevSoft\FB_tests\Firebird-4.0.0.2133-0_x64>isql -user sysdba -password masterkey localhost:employee
Database: localhost:employee, User: SYSDBA
SQL> alter session reset;
Statement failed, SQLSTATE = 01002
Cannot reset user session
-There are open transactions (2 active)
SQL>
Given the requirement that there is no active transaction (or only the current transaction executing ALTER SESSION RESET), it looks like ISQL needs to get special treatment for handling ALTER SESSION RESET, for example on detection of ALTER SESSION RESET, commit both transaction, or something similar.
The text was updated successfully, but these errors were encountered: