Some SQL Interface fixes...

[gitcodehelp]

1. For Settings > SQL Interface > Export, a menu option 'SQL dump of media' is missing for
   main.py: sql_dump mode == "dumpsqlmedia"

2. INSERT queries made via the SQL Interface render the cached pk values out-of-date, which can cause 'ID already used' errors the next time the program does an insert using get_id_cache_pk. For self-hosted ASM, I can clear memcache via the server command line, but for web-hosted this has to be done in the source.

So, in main.py: exec_sql/exec_sql_from_file, can we add something like:

if Execute/Execute Script did inserts, then (after the script is done) do:

1. DELETE from primarykey; (clear pk table)
2. asm3.cachemem.delete (for all keys)

For good measure, perhaps this cache clearing should also be done in asm3.dbupdate.reset_db ?

Thanks.

[bobintetley]

1. This is deliberate - there can be many gigabytes of media data.

There are two arguments you can pass to cron.py at the command line to export media, either maint_db_dump_dbfs_base64 (which outputs the dbfs table with base64 encoded contents), or maint_db_dump_dbfs_files which dumps the media as files to /tmp/dump_dbfs_files

2. Strangely, we already spotted and fixed this the other day. The ttl for cache_pk is now very short (60 seconds) to fix this.

[gitcodehelp]

Sorry, my test installation did not have the recent 60s ttl fix applied -- thanks.