Steps to duplicate (must have memcached enabled): 1. Create and save a report using the default values for "Report is public" and cache time. 2. Run the report. 3. Edit the report changing the setting for "Report is public" to yes. 4. Save the report. The cache time is now 0. 5. Edit the report changing the cache time to 300. 6. Save the report. The cache time is now 0 again. This seems to be due to the fact that cache_expiry is not passed to the update_sql function in the phase 'Update SQL'.
Data is lost.. upgrading severity.
Created attachment 44709 [details] [review] Bug 14735: Save cache_expiry on modifying a report The cache_expiry is not saved when updating a SQL report. Test plan: 0/ Enable memcached 1/ Create a sql report 2/ Edit it and change the cache expiry value 3/ Edit again => The value should have been updated.
Created attachment 44715 [details] [review] Bug 14735: Save cache_expiry on modifying a report The cache_expiry is not saved when updating a SQL report. Test plan: 0/ Enable memcached 1/ Create a sql report 2/ Edit it and change the cache expiry value 3/ Edit again => The value should have been updated. Signed-off-by: Frederic Demians <f.demians@tamil.fr> Repeatable bug. Solved with this patch.
Created attachment 44719 [details] [review] Bug 14735: Save cache_expiry on modifying a report The cache_expiry is not saved when updating a SQL report. Test plan: 0/ Enable memcached 1/ Create a sql report 2/ Edit it and change the cache expiry value 3/ Edit again => The value should have been updated. Signed-off-by: Frederic Demians <f.demians@tamil.fr> Repeatable bug. Solved with this patch. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Patch pushed to master. Enjoy your beer Jonathan!
This patch has been pushed to 3.20.x, will be in 3.20.6.
Pushed to 3.18.13, and released.