Dory SQLite Database Support
Dory supports local SQLite database files for development, prototypes, demos, test data, and lightweight analysis. You can open .sqlite or .db files, browse tables, run SQL, inspect results, and save queries.
Best-Fit Use Cases
- Local development database inspection.
- Product prototypes and demo datasets.
- Small dataset exploration.
- Reproducible test data queries.
- Lightweight analysis without a remote database.
Connection Requirements
Provide an absolute path to the SQLite file. The Dory process must be able to read the file. In Docker, mount the file directory into the container and use the container path.
Supported Capabilities
| Capability | SQLite support |
|---|---|
| Connections | Absolute-path .sqlite / .db file connections. |
| Explorer | Tables, columns, and basic structure. |
| SQL Console | SQLite SQL execution and results. |
| AI Chat | Schema-grounded SQL generation and explanation. |
| Charts & Results | Visual analysis for query results. |
| Saved Queries | Save reusable SQLite SQL. |
Using SQLite in Docker
When Dory runs in Docker, the SQLite file must be mounted into the container. Use the container path in the Dory connection, not the host-only path.
FAQ
Why cannot Dory find my SQLite file?
Confirm that the path is absolute and readable by Dory. In Docker, confirm that the directory is mounted into the container.
Is SQLite suitable for team sharing?
SQLite is best for local files, demos, and lightweight analysis. For shared team environments, consider PostgreSQL, MySQL, ClickHouse, or another server database.