We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Submitted by: @dyemanov
Is related to QA41
The problem is related to LCK_expression locks. Index ID is not unique across database, so it shouldn't be used as a lock key.
Commits: a747534 2f1dc82
The text was updated successfully, but these errors were encountered:
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Sorry, something went wrong.
Fix Version: 2.1 Alpha 1 [ 10150 ]
Fix Version: 2.1.0 [ 10041 ] =>
Link: This issue is related to QA41 [ QA41 ]
Commented by: @pcisar
Dmitry, could you provide a test case for this one please? I can't reproduce on 2.0.0.
Commented by: @dyemanov
create table expt1 (col1 int);
create table expt2 (col2 int);
create index iexpt1 on expt1 computed (col1 + 1);
create index iexpt2 on expt2 computed (col2 + 1);
select * from expt1 where col1 + 1 = 0;
select * from expt2 where col2 + 1 = 0;
drop index iexpt2;
commit; -- lockup
Fix verified, test added.
status: Resolved [ 5 ] => Closed [ 6 ]
Workflow: jira [ 11642 ] => Firebird [ 15325 ]
QA Status: No test
QA Status: No test => Done successfully
No branches or pull requests