Felix Schumacher <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #7 from Felix Schumacher <> ---
I believe this can happen, when the QueryStats change while the list of stats
get sorted.

I see three ways to go:
 1. add synchronization, so that the stats don't change while the list gets
 2. extract the information to sort on from the QueryStats and sort on that
 3. make QueryStats immutable and change the QueryStats instances, when the
stats gets updated

The first path probably will slow down the execution of jdbc calls.
The second one will be more memory intensive, but relatively simple to
The third seems to be the one where we would have to do the most work.

I tend to go for option two. What do you think?

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to