Skip to content

Refactor to use GizmoSQLConnection class#699

Open
sjruhland wants to merge 1 commit into
malloydata:mainfrom
sjruhland:sr/use-gizmosql-connection-class
Open

Refactor to use GizmoSQLConnection class#699
sjruhland wants to merge 1 commit into
malloydata:mainfrom
sjruhland:sr/use-gizmosql-connection-class

Conversation

@sjruhland
Copy link
Copy Markdown
Contributor

Summary

  • Refactors GizmoSQL connection handling to use the dedicated GizmoSQLConnection class from @malloydata/db-duckdb
  • Removes the useGizmoSQL flag approach in favor of separate class instantiation
  • Adds validation for required GizmoSQL fields (URI, username, password)

Changes

  • Updates import from DuckDBConnection to GizmoSQLConnection
  • Adds validation that throws errors for missing required configuration
  • Simplifies options object to match GizmoSQLConnectionOptions interface
  • Cleans up password redaction logic

Context

This aligns the VSCode extension with the architectural pattern where different client implementations use separate connection classes (similar to DuckDBWASMConnection), rather than embedding alternative backends in a single class.

Depends on: malloydata/malloy#2582

Updates GizmoSQL connection to use the dedicated GizmoSQLConnection class
from @malloydata/db-duckdb instead of DuckDBConnection with a useGizmoSQL flag.

This follows the established pattern where different client libraries use
separate connection classes (similar to DuckDBWasmConnection).

Signed-off-by: Schyler Ruhland <schyler@summation.com>
@sjruhland sjruhland force-pushed the sr/use-gizmosql-connection-class branch from 757e54f to 94f247b Compare December 1, 2025 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant