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
Current code ignores databases with DBB_bugcheck flag - i.e. for new attaches new database is created. This is unsafe cause in SS for some time coexist 2 database blocks using same database file, and among others may cause mentioned deadlock.
Can't get any reference on client side about Database instances that are assigned to attachment, --> can not check that new attachment get reference to the same Db object rather that to new (as it was before fix).
Value of _db_handle can be obtained in fdb, but its value is the same on FB builds before and after fix.
Discussed with dimitr and alex, letters 13.12.2018 - 26.12.2018
The text was updated successfully, but these errors were encountered:
Test Details: Sent letter to dimitr and alex, 13.12.18 08:30. Waiting for reply. => Can't get any reference on client side about Database instances that are assigned to attachment, --> can not check that new attachment get reference to the same Db object rather that to new (as it was before fix).
Value of _db_handle can be obtained in fdb, but its value is the same on FB builds before and after fix.
Discussed with dimitr and alex, letters 13.12.2018 - 26.12.2018
Submitted by: Basil A. Sidorov (basid)
Current code ignores databases with DBB_bugcheck flag - i.e. for new attaches new database is created. This is unsafe cause in SS for some time coexist 2 database blocks using same database file, and among others may cause mentioned deadlock.
Commits: 2ce876c ef57295
====== Test Details ======
Can't get any reference on client side about Database instances that are assigned to attachment, --> can not check that new attachment get reference to the same Db object rather that to new (as it was before fix).
Value of _db_handle can be obtained in fdb, but its value is the same on FB builds before and after fix.
Discussed with dimitr and alex, letters 13.12.2018 - 26.12.2018
The text was updated successfully, but these errors were encountered: