matrix-org / matrix-org/seshat
Question: Best way to recover seshat databases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 127
- Forks
- 29
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 3
Description
This is more of a Question than a Feature Request, I wasn't sure where to ask
What's the best way to import events from an older events.db? I've had this break too many times and would like to reconcile my events.db when I update and it inevitably breaks.
Outside of manually using sqlcipher and exporting events and manually importing them, this breaks the internal counter.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file, test, or entry point; begin by examining how events.db and its internal counter are handled, then compare that with the described sqlcipher export/import workflow. Done would require a defined, reliable way to import events from an older events.db without breaking the internal counter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100