Database connections
Supported databases
Choose a source with a clear view of what is implemented, where it runs, and what still needs verification.
What this catalogue verifies
Implementation reviewed at CLI revision eac96bf15e29 (restricted source). This is a source review, not a live provider certification or a claim about every released binary.
CLI support does not establish browser or hosted availability. Customer database connections in the browser and hosted service are not verified by this review. Firestore persistence inside DataTug is separate from querying your Firestore database.
| Source | Schema scan | Query path | Requirements and limits | Evidence |
|---|---|---|---|---|
| SQLiteImplemented path | Implemented | CLI read-only SQL and TugQL | Local database files. Capabilities depend on the command and access policy. | Restricted source ↗ |
| PostgreSQLImplemented path | Implemented | CLI read-only SQL and TugQL | CLI schema scan and read-only query paths are implemented. Server reads require unrestricted access (--no-policies); do not assume row or column policy enforcement. | Restricted source ↗ |
| MySQLImplemented path | Implemented | CLI read-only SQL and TugQL | CLI schema scan and read-only query paths are implemented. Server reads require unrestricted access (--no-policies); do not assume row or column policy enforcement. | Restricted source ↗ |
| OracleImplemented path | Implemented | CLI read-only SQL and TugQL | CLI schema scan and read-only query paths are implemented. Server reads require unrestricted access (--no-policies); do not assume row or column policy enforcement. | Restricted source ↗ |
| SQL ServerImplemented path | Implemented | CLI read-only SQL and TugQL | CLI schema scan and read-only query paths are implemented. Server reads require unrestricted access (--no-policies); do not assume row or column policy enforcement. | Restricted source ↗ |
| BigQueryImplemented path | No general scan claim | Dedicated CLI preview → approve → run | Explicit authentication, execution project, byte cap and reviewed source profile required. Bounded scalar queries; not the generic --db query dispatcher. Copy/compare support is operation-specific; this page does not certify it. | Restricted source ↗ |
| DuckDBImplemented path | Not verified here | CLI native SQL | Requires a cgo-enabled build and unrestricted access. Availability differs by build. | Restricted source ↗ |
| inGitDBImplemented path | Not supported by the scan command | CLI collection queries | Local project directories through DALgo; SQL support is not implied. | Restricted source ↗ |
| REST APIsImplemented path | Not applicable | Project HTTP queries | Reads saved HTTP query definitions from a project directory; recorded fixtures may be used on request failure. This is not arbitrary URL querying. | Restricted source ↗ |
| OpenVaultDBLimited / separate integration | Not verified here | Source adapter implemented | Dispatcher support exists. No live provider acceptance or hosted availability is certified by this catalogue. | Restricted source ↗ |
| FirestoreLimited / separate integration | No general CLI scan claim | Terminal browsing implemented; general CLI query not wired | Authenticated terminal UI lists root collections and reads up to 100 documents per collection. This is an existing customer Firestore browsing path; direct query run through the generic CLI dispatcher is not wired. Browser and hosted customer-query availability remain unverified here. | Restricted source ↗ |
| MongoDBUnverified connector | Not verified | No direct connector verified | No supported direct customer connector established by this implementation review. HTTP project queries do not certify a dedicated connector. | Restricted source ↗ |
| RedisUnverified connector | Not verified | No direct connector verified | No supported direct customer connector established by this implementation review. HTTP project queries do not certify a dedicated connector. | Restricted source ↗ |
| SnowflakeUnverified connector | Not verified | No direct connector verified | No supported direct customer connector established by this implementation review. HTTP project queries do not certify a dedicated connector. | Restricted source ↗ |
| DatabricksUnverified connector | Not verified | No direct connector verified | No supported direct customer connector established by this implementation review. HTTP project queries do not certify a dedicated connector. | Restricted source ↗ |
| AirtableUnverified connector | Not verified | No direct connector verified | No supported direct customer connector established by this implementation review. HTTP project queries do not certify a dedicated connector. | Restricted source ↗ |
| Google SheetsUnverified connector | Not verified | No direct connector verified | No supported direct customer connector established by this implementation review. HTTP project queries do not certify a dedicated connector. | Restricted source ↗ |
How this stays current
The homepage reads the same capability catalogue. Implementation links currently require repository access. The weekly evidence workflow uses the existing release GitHub App with a short-lived Contents: read token scoped to the implementation repository. Its first hosted run is pending verification; committed configuration alone does not establish active monitoring. Locally, an authorized maintainer can run node apps/app/scripts/check-database-evidence.mjs using an authenticated gh session. The checker compares all pkg/, apps/, internal/ and commercial/ implementation files plus dependency manifests, including additions and deletions. A change requests review; it does not prove or upgrade a capability.
To update: inspect changed command dispatch, policy checks and tests; revise the catalogue and pinned revision together; run the offline tests and optional upstream check. Add live execution receipts before claiming provider, browser or hosted acceptance.
Review the catalogue · Evidence check history · CLI commands