-
-
Notifications
You must be signed in to change notification settings - Fork 233
MON$DATABASE returns outdated transaction counters [CORE1926] #2360
New issue
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? Sign in to your account
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovFix Version: 2.5 Alpha 1 [ 10224 ] |
Modified by: @pmakowski |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @dyemanov
Is related to QA227
Fields MON$NEXT_TRANSACTION etc contain incorrect (outdated) numbers on Classic if there are other active attachments.
Test case:
- establish connection #1
- establish connection #2
- conn#2: select MON$NEXT_TRANSACTION from MON$DATABASE
- conn#2: commit
- conn#2: select MON$NEXT_TRANSACTION from MON$DATABASE
The number is still the same.
Commits: fda300f 2208b35 2279fde 669ec15
The text was updated successfully, but these errors were encountered: