"ALTER TABLE foo DROP COLUMN bar" syntax not supported in Databricks dialect · Issue #6457 · sqlfluff/sqlfluff · GitHub
More Web Proxy on the site http://driver.im/
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
This happens in Databricks SQL. In some other dialects, however, this syntax is supported.
I tried mysql, snowflake and clickhouse. They all work fine. This syntax was implemented for those dialects recently in #6348 , but it looks like Databricks SQL was not included in that PR.
KenHBS
changed the title
ALTER TABLE foo DROP COLUMN bar syntax not supported in Databricks dialect
"ALTER TABLE foo DROP COLUMN bar" syntax not supported in Databricks dialect
Nov 14, 2024
fstg1992
pushed a commit
to fstg1992/sqlfluff
that referenced
this issue
Nov 15, 2024
Search before asking
What Happened
When linting
ALTER TABLE foo DROP COLUMN bar;
using the Databricks dialect, I getAccording to the Databricks documentation, this syntax is allowed: https://docs.databricks.com/en/sql/language-manual/sql-ref-syntax-ddl-alter-table-manage-column.html#required-permissions
Expected Behaviour
I expect the linting to pass:
Observed Behaviour
The linting fails due to an unparseable section:
How to reproduce
fails, but
works
Dialect
This happens in Databricks SQL. In some other dialects, however, this syntax is supported.
I tried
mysql
,snowflake
andclickhouse
. They all work fine. This syntax was implemented for those dialects recently in #6348 , but it looks like Databricks SQL was not included in that PR.Version
3.2.5
Configuration
dialect = "databricks"
templater = "jinja"
max_line_length = 150
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: