Changes between Version 6 and Version 9 of Ticket #12
- Timestamp:
- Nov 2, 2009, 3:32:16 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12
-
Property
Priority
changed from
minor
tomajor
-
Property
Milestone
changed from
0.3 - Asset management
to0.4 - Functionality and integration
-
Property
Summary
changed from
After an update or save sometimes the old data/vaules are shown
toAfter an update or save sometimes old/stale data/vaules are shown
-
Property
Priority
changed from
-
Ticket #12 – Description
v6 v9 1 1 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. 2 2 3 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. 3 This is not due to query caching, as previously believed. (Higher level caching is on in the global config but still needs to be turned on for each case where it is wanted). 4 5 The solution is to add flush:true to save(), implemented in r178 as per http://jira.codehaus.org/browse/GRAILS-5111