| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Replace `unsafe` impl of backups with `rusqlite`. | Owen Jacobson | 2024-10-05 |
| | | | | | The unsafe code still exists, but I have more faith in the rusqlite authors than in myself to ensure that the code is correct. | ||
| * | Implement `sqlite3_backup_step`'s multi-step protocol. | Owen Jacobson | 2024-10-05 |
| | | |||
| * | Use the right functions for determining error messages. | Owen Jacobson | 2024-10-05 |
| | | |||
| * | Improve ergonomics of `Backup` | Owen Jacobson | 2024-10-05 |
| | | |||
| * | Limit unsafe{} blocks even more tightly. | Owen Jacobson | 2024-10-05 |
| | | |||
| * | Remove an unchecked operation in favour of a panic | Owen Jacobson | 2024-10-05 |
| | | |||
| * | Tighten up `unsafe{}` blocks in backup logic. | Owen Jacobson | 2024-10-05 |
| | | |||
| * | Make a backup of the `.hi` database before applying migrations. | Owen Jacobson | 2024-10-05 |
| This was motivated by Kit and I both independently discovering that sqlite3 will happily partially apply migrations, leaving the DB in a broken state. | |||
 |
index : pilcrow | |
| Run-It-Yourself web chat, maybe |
| summaryrefslogtreecommitdiff |