|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Classic only, any platform
|
|
Issue Links:
|
Relate
|
|
|
|
This issue is related to:
|
|
|
|
|
|
|
|
| Planning Status: |
Unspecified
|
|
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.
|
|
Description
|
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. |
Show » |
| The cvs commits can not be displayed for repository Firebird at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.
|
|
Bug
MON$DATABASE returns outdated transaction counters
