Opened 8 years ago
Closed 8 years ago
#2002 closed enhancement (fixed)
Change history logging should use batch API instead of Hibernate
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 3.8 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
I think this could improve performance of change history logging when there are a lot of changes in a single transaction. See #2000.
Change History (3)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
All tests have now been completed successfully.
Note:
See TracTickets
for help on using tickets.
(In [7132]) References #2002: Change history logging should use batch API instead of Hibernate
The
LogControlclass now uses aPreparedStatementwith SQL from the configuration files. The large test case from #2000 seems to be improved by 1-2 minutes.