Opened 8 years ago
Closed 8 years ago
#2020 closed defect (fixed)
Incorrect count in change history
| Reported by: | Nicklas Nordborg | Owned by: | everyone |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 3.9.1 |
| Component: | core | Version: | 3.8 |
| Keywords: | Cc: |
Description
The change history count can be incorrect due to changes in #2002.
It is the caching system used by Hibernate that is the culprit here. The count queries are configured to be cached by Hibernate. Normally this is not a problem since Hibernate knows when things change and can evict entries in the cache when it is needed. In #2002 we changed to logging implementation to bypass Hibernate and use direct SQL instead.
It seems like this may cause Hibernate to hold on to cached values and return incorrect results. The logging system need to force the cache to be evicted whenever new log entries are created. A similar issue was solved for annotations in [7127] (#2000)
Change History (2)
comment:1 by , 8 years ago
| Version: | → 3.8 |
|---|
comment:2 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [7181]) Fixes #2020: Incorrect count in change history