-
Notifications
You must be signed in to change notification settings - Fork 15.2k
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
Conversation
fb0c430
to
b5ade6f
Compare
"mssql": Dialects.TSQL, | ||
"mysql": Dialects.MYSQL, | ||
"netezza": Dialects.POSTGRES, | ||
"oceanbase": Dialects.MYSQL, |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto here
SUMMARY
Update the DB engine spec -> sqlglot dialect map.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION