Skip to content

Multi-engine dialect abstraction (post-1.0) #11

Description

@WailedParsley36

PostgreSQL is the only engine today; the parser visitors and command builders are Postgres-specific. Design a dialect seam so additional engines can be added without breaking the public API frozen at 1.0 (which is part of why the API lockdown, #2, matters now). Worth a design discussion before any implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    architectureArchitecture / designdiscussionNeeds discussion before work starts

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions