A SQLite connection is a path on the server
There is no network protocol, so the form collapses to one input and a remote user of a hosted deployment cannot open a file from their own machine.
6 posts
Writing on SQLite
The embedded engine — a file, no network. Full editor, ER diagrams, EXPLAIN and agent mode. Where it stops: There is no server to monitor: health reads file size and pragma statistics only.
A SQLite plan tree with no numbers on it
The query plan returns step descriptions and nothing else, so the rendering shows structure and answers index questions rather than cost questions.
On a shared instance a SQLite path is an access decision
Path validation rejects a null byte and nothing else, so any logged-in user can open any SQLite file the Studio process is able to read.
Why the SQLite editor has no transaction controls
The provider holds no session across two requests, so the begin, commit and rollback controls are withheld rather than offered and then failed.
There is no SQLite server to monitor
Health is an integrity check, a journal mode and file sizes, and one per-table figure depends on which built-in driver the deployment is running.
Two controls, because one was not enough on SQLite
A read-only open reads the query-only pragma back as off, so the profile sets it too and re-verifies it before every statement it sends.