Connecting to a hosted libSQL database with a token
The credential is an auth token rather than a password and the database is the host, so the dialog renders no user name and no database input at all.
4 posts
Writing on libSQL
SQLite's dialect over the network — Turso and self-hosted sqld, spoken natively. Where it stops: Monitoring is limited to what the sqld server itself exposes.
Connecting to a self-hosted libSQL server
A server started without authentication takes no token at all, and sending an empty one is rejected rather than treated as an anonymous connection.
On libSQL: read-only is a credential you create
The server refuses the pragma a database-native read-only profile depends on, so the boundary moves from the session to the token the database issues.
Stateless requests mean there is no session to count
Active connections are absent rather than zero and no connection ceiling is published, while table and index bytes are real because the storage view answers.