[Koha-bugs] [Bug 1084] would be nice to remove records from breeding tables.

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Apr 9 16:45:58 CEST 2012


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1084

--- Comment #7 from Michael Hafen <mdhafen at tech.washk12.org> ---
(In reply to comment #5)
> well spotted Katrin.
> 
> This could easily be achieved with the following SQL requests :
> 
> DELETE FROM import_records WHERE import_batch_id IN (SELECT
> import_batches.import_batch_id FROM import_batches WHERE
> import_batches.batch_type ="z3950") AND import_records.upload_timestamp<=
> DATE_SUB(now(), INTERVAL 1 DAY);
> 
> DELETE FROM import_batches WHERE import_batch_id NOT IN (SELECT DISTINCT
> import_batch_id from import_records);
> 
> The 1st request deletes all z3950 entries that are older than one day (too
> much from far, but harmless)
> The 2nd request deletes the "fake batch header" that is generated on each
> z3950 query
> 
> We can put those SQLs in 2 places:
> * on any z3950 search = before doing the new search, clean the database.
> Easy to setup, efficient, although a little loss of performances. I think
> this loss of performance is small compared to how long z3950 servers answer
> * add a script to cronjob, that cleans every night. A little bit harder to
> write, and has to be setup during installation, which put some pain to the
> sysadmin.
> 
> I prefer the 1st option, let me know which one you prefer.

Either the first option, or adding those sql statements to the cleanup_database
script with a default of 1 day.

Either of those options would be fine with me.  I think I'd prefer having it in
cleanup_database if only so the delay to removal can be set by the sysadmin. 
But I'm fine with which ever gets the job done.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are watching all bug changes.


More information about the Koha-bugs mailing list