1) can do this
2) and if a table not full dumped then start dump from last entry -> sqlmap resumes queries stored in session file to minimize number of repeated requests. We can't use "resume from last entry" as sqlmap sees everything as query<->reply
3) can't write to a dump file before the last row is retrieved because of formatting and filtering.
I can feel your frustration, but writing a partial table dump which would be totally different from the end formatted and filtered output would just start new issues.
I am trying to figure out a legitimate reason to dump 70K entries. Is this a requirement of some sort of a penetration test?
1) This also happens when extracting specific columns only and restarting. +1 for the overwrite confirmation.
@lukapusic with latest commit old table dumps are "backup"-ed. For example, after a couple of runs:
$ ll /home/stamparm/.sqlmap/output/testasp.vulnweb.com/dump/acuforum/users.csv*
-rw-rw-r-- 1 stamparm stamparm 921 Lip 5 12:36 /home/stamparm/.sqlmap/output/testasp.vulnweb.com/dump/acuforum/users.csv
-rw-rw-r-- 1 stamparm stamparm 854 Lip 5 12:34 /home/stamparm/.sqlmap/output/testasp.vulnweb.com/dump/acuforum/users.csv.1
-rw-rw-r-- 1 stamparm stamparm 921 Lip 5 12:36 /home/stamparm/.sqlmap/output/testasp.vulnweb.com/dump/acuforum/users.csv.2
Most helpful comment
I am trying to figure out a legitimate reason to dump 70K entries. Is this a requirement of some sort of a penetration test?