On 10-6-2018 12:36, Vlad Khorsun via Firebird-devel wrote:
Mark, all
I just committed changes as we discussed above. I.e. session reset
now ignores
prepared transactions, rollback currently active user transaction and
start new
one, issue warning if user transaction made changes in
Mark, all
I just committed changes as we discussed above. I.e. session reset now ignores
prepared transactions, rollback currently active user transaction and start new
one, issue warning if user transaction made changes in tables.
Here is how it looks now:
SQL> alter session reset;
On 4-6-2018 11:49, Vlad Khorsun via Firebird-devel wrote:
02.06.2018 19:54, Mark Rotteveel wrote:
JDBC API requires that statements are executed in a transaction. In
theory I can break that rule, but the problem with that is that it
requires explicit handling, which is 1) annoying to do and 2)
02.06.2018 19:54, Mark Rotteveel wrote:
On 2-6-2018 17:56, Vlad Khorsun via Firebird-devel wrote:
02.06.2018 18:07, Mark Rotteveel wrote:
I just saw the following commit:
https://github.com/FirebirdSQL/firebird/commit/bbf8348817c4592999fc137b18ba1be7326ad42d
This disallows execution of ALTER
On 2-6-2018 17:56, Vlad Khorsun via Firebird-devel wrote:
02.06.2018 18:07, Mark Rotteveel wrote:
I just saw the following commit:
https://github.com/FirebirdSQL/firebird/commit/bbf8348817c4592999fc137b18ba1be7326ad42d
This disallows execution of ALTER SESSION RESET if there are
02.06.2018 18:07, Mark Rotteveel wrote:
I just saw the following commit:
https://github.com/FirebirdSQL/firebird/commit/bbf8348817c4592999fc137b18ba1be7326ad42d
This disallows execution of ALTER SESSION RESET if there are transactions
active. I think this is too restrictive.
Only from
I just saw the following commit:
https://github.com/FirebirdSQL/firebird/commit/bbf8348817c4592999fc137b18ba1be7326ad42d
This disallows execution of ALTER SESSION RESET if there are
transactions active. I think this is too restrictive.
For example, in Jaybird queries executed through the
