Issue Details (XML | Word | Printable)

Key: CORE-2305
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dmitry Yemanov
Reporter: Carlos H. Cantu
Votes: 1
Watchers: 1

If you were logged in you would be able to see more operations.
Firebird Core

Make mon$statement_id value constant among monitoring snapshots

Created: 04/Feb/09 04:05 PM   Updated: 27/May/15 04:45 PM
Component/s: Engine
Affects Version/s: 2.1.0, 2.1.1, 2.1.2, 2.1.3, 3.0 Initial, 2.5.0
Fix Version/s: 2.5.1, 3.0 Alpha 1

QA Status: Done with caveats
Test Details:
See comment in .fbt:

        -- todo later, after fix CORE-4796
        'merge into tdetl t '
        || 'using ( select 5 as id, 1 as pid from rdb$types rows 2 ) s '
        || 'on '
        || 'when matched then update set = '
        || 'when not matched then insert values(,';

 Description  « Hide
The value of mon$statement_id may change for the same running statement in different "monitoring snapshots". This makes difficult, for example, for monitoring applications to identify the same query, since it keeps "refreshing" the data by closing and opening the monitoring transaction and so, may get different numbers for the mon$statement_id,

BTW, Dmitry Yemanov told me that the currently behavior may change in 2.5. I'm adding this to the tracker so he will not forget about it ;-)

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Douglas Tosi added a comment - 04/Feb/09 05:06 PM
If I could vote 1.000 times for this issue, I would.
The current behavior is really counter intuitive (not to mention it's a royal PITA). I should know, I work with monitoring tables all day long. ;)