bjoern 9135cffaa4 do not change db schema in an incompatible way (#5254) ...

PR #5099 removed some columns in the database that were actually in use.

usually, to not worsen UX unnecessarily
(releases take time - in between, "Add Second Device", "Backup" etc.
would fail), we try to avoid such schema changes (checking for
db-version would avoid import etc. but would still worse UX),
see discussion at #2294.

these are the errors, the user will be confronted with otherwise:

<img width=400
src=https://github.com/deltachat/deltachat-core-rust/assets/9800740/e3f0fd6e-a7a9-43f6-9023-0ae003985425>

it is not great to maintain the old columns, but well :)

as no official releases with newer cores are rolled out yet, i think, it
is fine to change the "107" migration
and not copy things a second time in a newer migration.

(this issue happens to me during testing, and is probably also the issue
reported by @lk108 for ubuntu-touch)

2024-02-13 23:00:47 +01:00

..

migrations.rs

do not change db schema in an incompatible way (#5254)

2024-02-13 23:00:47 +01:00

pool.rs

sql: organize connection pool as a stack rather than a queue

2023-02-20 15:00:37 +00:00

tables.sql

Securejoin: store bobstate in database instead of context

2022-03-01 23:02:40 +01:00