#12 closed defect (fixed)
After an update or save sometimes the old data/vaules are shown — at Version 6
Reported by: | Gavin | Owned by: | Gavin |
---|---|---|---|
Priority: | major | Milestone: | 0.4 - Functionality and integration |
Component: | gnuMims - application general | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
A browser refresh causes the new data to be shown, so the data is persisted but just not fetched in time to show updated values after redirect.
This is due to query caching, the query_cache has been turned off as of r171. This may lower performance and query caching may be improved in future versions of Grails so may be turned on again in future.
Change History (6)
comment:1 Changed 16 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 16 years ago by
Version: | → trunk |
---|
comment:3 Changed 16 years ago by
comment:4 Changed 16 years ago by
Milestone: | → 0.3 - Asset management |
---|
comment:5 Changed 15 years ago by
Owner: | set to Gavin |
---|---|
Status: | new → accepted |
This is most likely due to caching in hibernate and if problem persists can be turned off in DataSource?.groovy
comment:6 Changed 15 years ago by
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
So far this has only shown up in development mode, the deployed war running an in memory hsqldb does not appear to have this problem.