Recognize externally-dropped databases from driver errors and the health check
Maintainers usually reply within 1 day
@debba is already working on this.
Since Jul 24, 2026.
Assessment
This issue has not been assessed yet.
Description
Follow-up 2 of #524 (see also #518). Builds on #525 — reuses the same prune/tear-down flow.
Databases dropped outside the app are currently invisible: drivers stringify every error, so a missing database is indistinguishable from a typo, and the health check keeps passing.
Scope:
- Add a structured "database not found" error classification in the drivers: MySQL errno 1049/1046, Postgres SQLSTATE 3D000, SQLite unable-to-open. Query/metadata failures with this classification trigger the same flow as #525 (prune one database from a multi-db selection, or tear down a single-db session).
- Make the health check able to see it:
- MySQL pings with COM_PING, which keeps succeeding after the current database is dropped — the ping should touch the current database instead.
- SQLite pings through the still-open file handle — the ping should check the file still exists.
- The health check must distinguish "server unreachable" (tear down the connection) from "one database missing" (prune just that one), instead of tearing everything down after two failed pings.
"Disconnected" means the session, not the saved connection: if the database is recreated later, the saved connection must work again unchanged.
- Dominant language
- TypeScript
- Stars
- 5.1k
- Forks
- 335
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 62
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from TabularisDB/tabularis
-
feature request good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TabularisDB/tabularis#853 ·
Maintainers usually reply within 1 day
-
Update the logo across the app: icons, dock, installers and in-app brandingPossibly taken @wajrock claimed this today. Openenhancement
TabularisDB/tabularis#873 · 1 assignee ·
Maintainers usually reply within 1 day
-
feature request help wanted
Difficulty 4/5 3-5 days Newbie friendliness 68/100
TabularisDB/tabularis#871 ·
Maintainers usually reply within 1 day
-
feature request good first issue
Difficulty 3/5 1-2 days Newbie friendliness 74/100
TabularisDB/tabularis#870 ·
Maintainers usually reply within 1 day
-
feature request help wanted
Difficulty 4/5 3-5 days Newbie friendliness 58/100
TabularisDB/tabularis#869 ·
Maintainers usually reply within 1 day
All issues in TabularisDB/tabularis
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/docs#46222 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready area: config area: skills type: chore upstream: brain-kit
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug escritorio mapa
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
marcosferr/reporte-ciudadano#4 · 1 comment ·
-
area: material/sort gemini-triaged needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
angular/components#33933 ·
Maintainers usually reply within 1 day