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.
For the new command to execute statements in external databases
EXECUTE STATEMENT ' ... ' ON EXTERNAL 'mydb.fdb';
the documentation says
... started new transaction with the same parameters as current transaction ...
but it ignores WAIT parameter. I guess it is by design because of impossibility
to detect deadlocks between two databases, right ?
But it also ignores this parameter
SET TRANSACTION LOCK TIMEOUT 5
Is it intentional ?
summary: Wait mode and lock timeout of external transaction of EXECUTE STATEMENT not matched to corresponding parameters o flocal transaction => Wait mode and lock timeout of external transaction of EXECUTE STATEMENT not matched to corresponding parameters of local transaction
Submitted by: @hvlad
Reported by Ivan Prenosil at fb-devel :
For the new command to execute statements in external databases
EXECUTE STATEMENT ' ... ' ON EXTERNAL 'mydb.fdb';
the documentation says
... started new transaction with the same parameters as current transaction ...
but it ignores WAIT parameter. I guess it is by design because of impossibility
to detect deadlocks between two databases, right ?
But it also ignores this parameter
SET TRANSACTION LOCK TIMEOUT 5
Is it intentional ?
Commits: 2dbab96 087a7f7
====== Test Details ======
NB: parameter NO AUTO UNDO not passed from 'outer' Tx to autonomous one. See script in the letter to dimitr 26-mar-2015 09:38.
The text was updated successfully, but these errors were encountered: