After an update or save sometimes old/stale data/vaules are shown
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 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).
The solution is to add flush:true to save(), implemented in r178 as per http://jira.codehaus.org/browse/GRAILS-5111
Change History (9)
Description: |
modified (diff)
|
Milestone: |
→ 0.3 - Asset management
|
Owner: |
set to Gavin
|
Status: |
new →
accepted
|
Description: |
modified (diff)
|
Resolution: |
→ fixed
|
Status: |
accepted →
closed
|
Resolution: |
fixed
|
Status: |
closed →
reopened
|
Summary: |
After an update or save sometimes the old data/vaules are shown →
After an update or save sometimes old/stale data/vaules are shown
|
Milestone: |
0.3 - Asset management →
0.4 - Functionality and integration
|
Description: |
modified (diff)
|
Priority: |
minor →
major
|
Resolution: |
→ fixed
|
Status: |
reopened →
closed
|
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.