You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched the issues and found no similar issues.
Description
MariaDB has some small syntactic differences compared to MySQL, but for the most part should be very similar. I have run into issues where the linter throws unparsable section errors because of the presence of CREATE OR REPLACE TABLE statements, because MySQL doesn't support the OR REPLACE syntax.
There are many more instances where parsing errors happen due to small differences between these dialects.
Would it be preferrable to add to the existing MySQL syntax, or to create a whole new dialect specifically for the small MariaDB changes?i
Use case
mariadb dialect added that borrows heavily from mysql but with syntax differences accounted for.
Dialect
MySQL
Are you willing to work on and submit a PR to address the issue?
Search before asking
Description
MariaDB has some small syntactic differences compared to MySQL, but for the most part should be very similar. I have run into issues where the linter throws
unparsable section
errors because of the presence ofCREATE OR REPLACE TABLE
statements, because MySQL doesn't support the OR REPLACE syntax.There are many more instances where parsing errors happen due to small differences between these dialects.
Would it be preferrable to add to the existing MySQL syntax, or to create a whole new dialect specifically for the small MariaDB changes?i
Use case
mariadb
dialect added that borrows heavily frommysql
but with syntax differences accounted for.Dialect
MySQL
Are you willing to work on and submit a PR to address the issue?
Code of Conduct
The text was updated successfully, but these errors were encountered: