Skip to content

chore: update sqlglot dialect map #33701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 5, 2025
Merged

chore: update sqlglot dialect map #33701

merged 1 commit into from
Jun 5, 2025

Conversation

betodealmeida
Copy link
Member

SUMMARY

Update the DB engine spec -> sqlglot dialect map.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@pull-request-size pull-request-size bot added size/XS and removed size/S labels Jun 5, 2025
@dosubot dosubot bot added the change:backend Requires changing the backend label Jun 5, 2025
Copy link

korbit-ai bot commented Jun 5, 2025

I was unable to post the issues I found. This could be because a force push or squash has changed the commit history since I scanned this pull request. You can get another review by commenting /korbit-review.

"mssql": Dialects.TSQL,
"mysql": Dialects.MYSQL,
"netezza": Dialects.POSTGRES,
"oceanbase": Dialects.MYSQL,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be ok, googled it and it seems they're aiming for a perfect replacement for MySQL so it should be fully compatible, but who knows 🤷 Don't think it would hold the PR just mentioning

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's my understanding. I think that even if these are not perfect matches it's better than using the generic parser.

# "ocient": ???
# "odelasticsearch": ???
"oracle": Dialects.ORACLE,
"parseable": Dialects.POSTGRES,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto here

@betodealmeida betodealmeida merged commit b00660a into master Jun 5, 2025
56 of 58 checks passed
@betodealmeida betodealmeida deleted the update-dialects branch June 5, 2025 17:14
ianngech pushed a commit to Pesapal-Ltd/superset that referenced this pull request Jun 10, 2025
LevisNgigi pushed a commit to LevisNgigi/superset that referenced this pull request Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change:backend Requires changing the backend size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants