Christian Schneider

At PC, pulled messenger.db (adb) can be vauum'd (but not with the pure command directly!) First I need to launch "end transaction" then "vacuum" ! That works and shrinks db...

As a containment action I pushed the external vacuum'd db back to the device. I hope this really helps because I'm not able to check the db into the device...

First one word to the following line: `09-06 00:22:53.971 E/DeltaChat(17171): Cannot excecute "END TRANSACTION;". SQLite says: cannot commit - no transaction is active` You see the word` commit` here. I...

Regarding the problem: There are two possible solutions to reduce or prevent the issue: 1) prevent extensive memory consumption on backup import - and 2) move or use external storage...

Oh, we are online ;-) I did the experience with sqlitebrowser and an offline file. From the documentation point of view it is the same, but from the reality there...

Additional informations regarding used file and software for the trials: - File: backup file from dc at download directory of device (copied to PC) - Software: sqlitebrowser from debian linux

Ok You proposed that for future backup file: [blob of original database file][attachments, ...] At first point of view this should be easy too to implement. But at the end...

yes, I know. I was surprised too. but if you look at log excerpt you can see that "end transaction" doesn't seem to work at the device in the same...

@r10s The more I think about your idea the better I find it :) But see the updated comment above! But too, if we would do now copy the messenger.db...

Another comment to the log a few days ago: ``` 09-06 00:22:53.971 E/DeltaChat(17171): Cannot excecute "END TRANSACTION;". SQLite says: cannot commit - no transaction is active 09-06 00:22:54.062 E/DeltaChat(17171): Cannot...