Skip to content

fix(deps): pin polyglot with column alias types in output order - #37

Closed
kvlonge wants to merge 1 commit into
mainfrom
fix/polyglot-column-alias-order
Closed

kvlonge wants to merge 1 commit into
mainfrom
fix/polyglot-column-alias-order

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Why

Polyglot's type annotation kept a CTE's or derived relation's columns in a hash map. A column alias list renames columns by position, so in FROM o AS t(a, b) each alias could take another column's type, and the types changed between runs. SQLBuild pins SQLClean and polyglot together, so both need the fixed polyglot to keep a single copy in its build.

Changes

Verification

  • The polyglot change adds a regression test that fails in 3 of 3 runs without the fix, and passes with it.
  • This repository's CI runs on this PR.

Polyglot 1cb2a731 keeps a CTE's or derived relation's columns in output
order, so a column alias list renames each column to the type it has.
Before, the alias types followed hash order and changed between runs.

kvlonge commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

Not needed: SQLBuild analysis is moving to SQLQuack.

@kvlonge kvlonge closed this Nov 7, 2026
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