TablePad 0.1.6 — Connections that stay in sync
v0.1.6LatestConnections
- Settings follow the engine — Postgres, MySQL, SQLite, Cloudflare D1, and the others each get their own fields instead of one generic host and port form
- A changed connection saves only after a successful test
- Saving clears stale caches on the server and in the client, and a failed database list shows an error with retry instead of an empty database
- Caches are keyed by host, port, and database, so editing a connection does not flash the previous database’s tables
Workspaces
- New workspaces take the connected database’s name instead of a generic title like “PostgreSQL workspace”
- Renaming in Settings sticks on the workspace itself, not only on the connection row
- The database landing and workspace header stay in sync when the connection changes, and Cloudflare D1’s internal
_cf_*tables stay hidden
Continuity
- UI preferences survive app updates — they reset only when the preference schema changes, not on every build
- Meta storage uses versioned migrations, including global LLM settings