Opened 10 years ago

Closed 9 years ago

#12 closed defect (fixed)

After an update or save sometimes old/stale data/vaules are shown

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 Gavin)

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)

comment:1 Changed 10 years ago by Gavin

Description: modified (diff)

comment:2 Changed 10 years ago by Gavin

Version: trunk

comment:3 Changed 10 years ago by Gavin

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.

comment:4 Changed 10 years ago by Gavin

Milestone: 0.3 - Asset management

comment:5 Changed 9 years ago by Gavin

Owner: set to Gavin
Status: newaccepted

This is most likely due to caching in hibernate and if problem persists can be turned off in DataSource?.groovy

comment:6 Changed 9 years ago by Gavin

Description: modified (diff)
Resolution: fixed
Status: acceptedclosed

comment:7 Changed 9 years ago by Gavin

Resolution: fixed
Status: closedreopened
Summary: After an update or save sometimes the old data/vaules are shownAfter an update or save sometimes old/stale data/vaules are shown

Turning off query caching appears to improve things in dev environment but when run in prod environment against MySQL with InnoDB problem is still there and more common.

comment:8 Changed 9 years ago by Gavin

Milestone: 0.3 - Asset management0.4 - Functionality and integration

comment:9 Changed 9 years ago by Gavin

Description: modified (diff)
Priority: minormajor
Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.