Changes between Version 1 and Version 6 of Ticket #12


Ignore:
Timestamp:
Oct 27, 2009, 1:57:27 PM (14 years ago)
Author:
Gavin
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #12

    • Property Status changed from new to closed
    • Property Version changed from to trunk
    • Property Milestone changed from to 0.3 - Asset management
    • Property Owner set to Gavin
    • Property Resolution changed from to fixed

  • Ticket #12 – Description

    v1 v6  
    1 Need to investigate if this happens when run against a MySql database. There is a bug report against grails that requires a flush:true when run against Postgresql. A browser refresh causes the new data to be shown, so it is persisted but just not fetched in time to show after redirect.
     1A 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
     3This 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.