Shutdown after a big scan takes too long (deleting ascan records)

[GoogleCodeExporter]

It can take a _Very_ long time to shut ZAP down after a big scan.
In this case observed after a scan that took 13 hours ;)
It looks like this is because ZAP is deleting all of the history records 
related to the scan - in ActiveScan.reset();
Not really sure why its doing this.
OK, it will reduce space but it takes far too long and the information might 
well be useful for historical purposes (eg, which didnt ZAP find this issue 
when we last ran it). We cant currently view previous scan results, but we 
could change ZAP to allow that if it would be useful.
So there should at least be an option not to delete these records, and it might 
even be better if this was the default.

Original issue reported on code.google.com by psii...@gmail.com on 26 Apr 2013 at 8:30

[GoogleCodeExporter]

Original comment by psii...@gmail.com on 26 Apr 2013 at 11:57

• Changed state: Committed

[GoogleCodeExporter]

When you say delete records I think database. Instead of deleting records why 
not just drop the table (and recreate it empty if ZAP needs it to exist)?

[Similar options must exist if we're simply speaking lines/rows in an array or 
matrix type data structure....simply close it, invalidate it, drop all it's 
entries, etc. instead of deleting one-by-one.]

Original comment by kingtho...@gmail.com on 2 May 2013 at 12:16

[GoogleCodeExporter]

In this case it's not possible to drop the table as it contains all the 
messages sent/received by the several ZAP components (proxy, spider, fuzzer, 
forced browse,...).

Original comment by THC...@gmail.com on 2 May 2013 at 2:10