Skip to content

fix: the PostgreSQL dialect names its version - #29

Merged
christiangda merged 1 commit into
mainfrom
fix/the-postgresql-dialect-names-its-version
Oct 24, 2026
Merged

christiangda merged 1 commit into
mainfrom
fix/the-postgresql-dialect-names-its-version

Conversation

@christiangda

Copy link
Copy Markdown
Contributor

DialectSQLStandard.String() is SQL:2023, and DialectPostgreSQL.String() was a bare PostgreSQL. The grammar is PostgreSQL 18's, and every rule is checked against PostgreSQL 18, so each dialect now names its version.

  • String() is PostgreSQL 18.
  • Docs that named the dialect without its version now name it:
    • the package doc;
    • configuration.md and getting-started.md;
    • the documentation index's diagram (rendered);
    • migration.md, which has a v1.1.0 → v1.1.1 note: only a caller that compares the string changes, and the grammar does not.

This is v1.1.1: v1.1.0 is already tagged and public, so it is not moved.

go test -race passes, and golangci-lint reports 0 issues.

🤖 Generated with Claude Code

DialectSQLStandard says SQL:2023 and DialectPostgreSQL said PostgreSQL:
the grammar is PostgreSQL 18's, checked against PostgreSQL 18, and its
name, the package doc, the guides and the documentation index's diagram
now say so. Only a caller that compares String() changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@christiangda christiangda self-assigned this Oct 24, 2026
@christiangda
christiangda merged commit 4c2f1ef into main Oct 24, 2026
1 check passed
@christiangda
christiangda deleted the fix/the-postgresql-dialect-names-its-version branch October 24, 2026 17:29
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