sqlitebrowser / sqlitebrowser/sqlitebrowser
[Bug]: When DB Browser freezes on a long query, it CLEARS your sqbpro file
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 24.6k
- Forks
- 2.4k
- Avg merge
- 3d 49m
- Merged PRs (30d)
- 3
Description
What did you do?
- Ran a long query
- Tried canceling
- DB Browser froze
- Terminated program
- sqbpro file goes to 0 bytes
What did you expect to see?
Not to zero out my file
What did you see instead?
It zeroed out my file. This is the SECOND time this has happened. The first time, I didn't have a backup of all my SQL, so I lost a TON of it and had to rewrite it all. That burned me good, so I have taken to backing up and even versioning my sqbpro file. It just happened again. While I still have my last backup, I still lost an hour's worth of SQL.
DB4S Version
3.12.2
What OS are you seeing the problem on?
Windows
OS version
Windows 7
Relevant log output
No response
Prevention against duplicate issues
- I have searched for similar issues
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the reported sequence in DB4S 3.12.2 on Windows 7: run a long query, cancel it, terminate the frozen program, and inspect the sqbpro file. Done means identifying why the file becomes 0 bytes and preserving its contents after this failure path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, sqlite
- Domain
- database, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100