Changelog: the second read covers the database phase too

This commit is contained in:
2026-10-22 19:48:22 +02:00
parent 133f5f9d34
commit 343389b98b
+2 -2
View File
@@ -16,8 +16,8 @@ instead carried by the app description, the git tag, the release, and this file.
effectively ran (02:30 UTC becomes 04:30 Europe/Berlin in summer) and nothing moves. effectively ran (02:30 UTC becomes 04:30 Europe/Berlin in summer) and nothing moves.
- A full restore over SMB stopped after 17 hours with "Decryption failed": a read over a long - A full restore over SMB stopped after 17 hours with "Decryption failed": a read over a long
line handed out wrong bytes (the backup itself was fine, the same files restored identically line handed out wrong bytes (the backup itself was fine, the same files restored identically
afterwards). A blob that does not decrypt as first read is now read once more on a request of afterwards). A blob that does not decrypt as first read, of a file or of the database, is now
its own, and only a second failure stops the restore. read once more on a request of its own, and only a second failure stops the restore.
- A full restore onto MySQL/MariaDB stopped with "Incorrect string value" when it created a table - A full restore onto MySQL/MariaDB stopped with "Incorrect string value" when it created a table
(of an app that is not installed here) whose rows hold emoji or other 4-byte characters: the (of an app that is not installed here) whose rows hold emoji or other 4-byte characters: the
table got 3-byte utf8. Tables the restore creates now get this installation's character set and table got 3-byte utf8. Tables the restore creates now get this installation's character set and