summaryrefslogtreecommitdiffstats
path: root/Changes
diff options
context:
space:
mode:
authorFlorian Pritz <bluewind@xinu.at>2019-02-07 16:20:39 +0100
committerFlorian Pritz <bluewind@xinu.at>2019-02-07 17:14:35 +0100
commit138ba53c92dc10c1b9b9bb31448b76f9bbac0ecd (patch)
tree17fb5831b180cb1418a2f5b38d6ce8dd09d28246 /Changes
parent93af313b49a44b83d13691fe870f8f8fe84e6f92 (diff)
downloadApp-BorgRestore-138ba53c92dc10c1b9b9bb31448b76f9bbac0ecd.tar.gz
App-BorgRestore-138ba53c92dc10c1b9b9bb31448b76f9bbac0ecd.tar.xz
DB/remove_archive: Properly handle cases where the DB is empty after removal
Empty here means that the DB does not contain any backup archive information because all information that is already in the db has to be removed. The old code tries to copy existing data into the new table, but since there are no archives to copy data for, the sql query fails. Also, it would copy all rows and only populate the path column, but if there are no archives that have timestamps, that's actually useless work. This patch ensures that the table is kept empty if there are no archives. Signed-off-by: Florian Pritz <bluewind@xinu.at>
Diffstat (limited to 'Changes')
-rw-r--r--Changes2
1 files changed, 2 insertions, 0 deletions
diff --git a/Changes b/Changes
index dae2435..c90d245 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+ - Properly handle cases where the DB is empty after removal of archive
+ information
3.2.1 2018-11-01T12:54:26Z
- Add missing version requirement to List::Util dependency