NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #1178 most downloaded on PyPI
The SQL Linter for Humans
Latest stable
4.5.0
Last release 16 days ago
30 Oct 2026
Ships fairly regularly
a new release about every 2 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
159 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
This minor release contains four particular changes of note:
This minor release contains four particular changes of note:
render_variant_limit is now 5 instead of 1, so SQLFluff may report new linting violations from templated branches that were previously not inspected in Jinja and dbt projects. Documentation for the feature is now also available in Template Variant Rendering.max_parse_nodes config setting to enable parsing of larger files in their project if necessary.AL10 rule requires aliases on FROM subqueries, because omitting them causes parse errors in most major dialects.Beyond that, there are parser improvements for T-SQL, PostgreSQL, Snowflake, BigQuery, DuckDB, ClickHouse, Oracle, Hive/SparkSQL, Databricks, DB2, Athena, Trino, MariaDB/MySQL, StarRocks, Teradata, and Greenplum. There are also rule fixes for ST06, ST11, LT02, and LT09, better handling for placeholder and dbt/Jinja rendering edge cases, and a new option to fail when files are skipped for size.
This release also includes first-time contributions from twenty new contributors. Thank you all for your contributions. 🏆
DECLARE ... CURSOR FOR (#7812) @copilot-swe-agent[bot]pool.join() is called in ParallelRunner (#7686) @peterbudALTER TABLE ... ENABLE|DISABLE TRIGGER (#7811) @copilot-swe-agent[bot]${...} parameter references (#7767) @copilot-swe-agent[bot]var() placeholders under Jinja subscripting (#7793) @copilot-swe-agent[bot]WITH clauses (#7761) @copilot-swe-agent[bot]json_object() pairs in Trino and Athena (#7764) @copilot-swe-agent[bot]OPTIONS in CREATE TABLE FUNCTION (#7776) @copilot-swe-agent[bot]FROM DUAL to parse as a table reference (#7763) @copilot-swe-agent[bot]WITH TAG on dynamic table columns without a data type (#7754) @copilot-swe-agent[bot]COLLATE in Databricks CREATE TABLE column properties (#7749) @copilot-swe-agent[bot]CHECK/NOCHECK CONSTRAINT ALL in T-SQL ALTER TABLE (#7748) @copilot-swe-agent[bot]UPDATE ALL BY NAME syntax for MERGE (#7756) @ninazacharia-toastYour coding agent can read these notes before it upgrades. Set up the MCP server →
chore: Update deprecated gitwildmatch to gitignore (#7673) @keraion
This minor release expands SQLFluff in four meaningful ways: recursion protection, more complete Rust-backed execution, broader dialect support, and better performance on large templated projects.
max_parse_depth config setting to enable deeper parsing in their project if necessary.Also, welcome to the nineteen new contributors! Thanks for your contributions! 🏆
vdebug behind verbose-debug feature (#7674) @keraiongitwildmatch to gitignore (#7673) @keraion:: cast (#7615) @copilot-swe-agent[bot]noqa and update docs (#7658) @mxrFROM ... INSERT ... multi-insert statements (#7633) @copilot-swe-agent[bot]SELECT * APPLY(...) (#7654) @copilot-swe-agent[bot]EXCEPT set expressions in Greenplum (#7632) @copilot-swe-agent[bot]ignore = templating disabling all lint rules with Python templater (#7617) @copilot-swe-agent[bot]IS [NOT] DISTINCT FROM comparison statement (#7556) @peterbudreturn dbt builtin (#7584) @mrichards42noqa directives in sqlfluff parse for PRS/TMP violations (#7604) @peterbudVALUES() function nested in expressions for ON DUPLICATE KEY UPDATE (#7603) @copilot-swe-agent[bot]CREATE TYPE ... FROM to support data types with precision/scale (#7596) @copilot-swe-agent[bot]CREATE EXTERNAL TABLE AS SELECT (CETAS) (#7595) @samgusickCREATE FULLTEXT STOPLIST statement support (#7574) @copilot-swe-agent[bot]json_array with NULL ON NULL and RETURNING clauses (#7561) @copilot-swe-agent[bot]line_position and keyword_line_position (#7555) @peterbudrequire_final_semicolon (#7534) @copilot-swe-agent[bot].pkb to default sql_file_exts (#7541) @copilot-swe-agent[bot]~) (#7520) @copilot-swe-agent[bot]DEFINE keyword (#7505) @robert-norbergOPENROWSET(BULK) options (#7491) @lynndb0ColonDelimiterSegment in JSON key-value pairs grammar (#7494) @peterbudplatformdirs to <4.6.0 (#7488) @peterbud%ROWTYPE parameters in Oracle. (#7476) @joaostorrerThis is a re-release of 4.0.1 which had issues in initial deployment.
This is a re-release of 4.0.1 which had issues in initial deployment.
Testing release to confirm functionality of rust publish script.
Testing release to confirm functionality of rust publish script.
[4.0.4a1] - 2026-02-08 Pre-release
Pre-release
Compare
This is a re-release of the planned 4.0.1 which failed to publish due to deploy pipeline issues.
This is a re-release of the planned 4.0.1 which failed to publish due to deploy pipeline issues.
Normally we would use a post-release but rust doesn't support that construct.
This is a post release of 4.0.1 to fix issues in the package publish pipeline.
This is a post release of 4.0.1 to fix issues in the package publish pipeline.
This major release brings support for internal rust optimisations. Rust support is still effectively in _beta_ and is available on an opt in basis. To
This major release brings support for internal rust optimisations. Rust support is still effectively in beta and is available on an opt in basis. To take advantage of these performance improvements, users can install sqlfluff[rs] to get the parser and lexer running in rust. The current implementation does yield noticeable gains on large files and projects - although for small individual files, the overhead of moving data into rust means that performance is a tiny bit slower. Functionality has proven fairly stable during pre release testing, and we anticipate that the rust implementations will become defaults from 5.0 onwards.
We advise testing the rust package in a development environment before going direct to production.
A massive shout out to @keraion, who's been leading the way on this effort.
Additionally in this release:
CREATE SYNONYM, DROP SYNONYM and ALTER SYNONYM statements in Oracle. (#7291) @joaostorrerCREATE TYPE and ALTER TYPE (#7314) @annebelleoNotImplementedError exception (#7285) @peterbudCREATE DATABASE LINK, DROP DATABASE LINK and ALTER DATABASE LINK statements in Oracle. (#7284) @joaostorrerENABLE/DISABLE clause after constraints in CREATE TABLE statements in Oracle. (#7250) @joaostorrerThis is an alpha release of SQLFluff 4.0 to continue verification of the rust portions of the codebase. In particular to verify the inclusion of a rus
This is an alpha release of SQLFluff 4.0 to continue verification of the rust portions of the codebase. In particular to verify the inclusion of a rust parser. Rust support is still in beta, but from this release, users can install sqlfluff[rs] to get the parser and lexer running in rust. Current implementation does yield noticeable gains on large files and projects - although for small individual files, the overhead of moving data into rust means that performance is a tiny bit slower.
We do not recommend that users install this release except for testing and evaluation.
Big thanks to @keraion, who's been leading the way on this effort.
Additionally in this release:
These will be added to the changelog properly in the full 4.0.0 release.
CREATE SYNONYM, DROP SYNONYM and ALTER SYNONYM statements in Oracle. (#7291) @joaostorrerCREATE TYPE and ALTER TYPE (#7314) @annebelleoNotImplementedError exception (#7285) @peterbudCREATE DATABASE LINK, DROP DATABASE LINK and ALTER DATABASE LINK statements in Oracle. (#7284) @joaostorrerENABLE/DISABLE clause after constraints in CREATE TABLE statements in Oracle. (#7250) @joaostorrerThis is an alpha release of SQLFluff 4.0 to continue verification of the rust portions of the codebase. In particular to verify version locking of pyp
This is an alpha release of SQLFluff 4.0 to continue verification of the rust portions of the codebase. In particular to verify version locking of pypi packages works, and testing users can verify that Rust is working easily. Rust support is still in beta, but from this release, users can install sqlfluff[rs] to get some of the parser running in rust. Current implementation is not expected to yield significant gains but we do expect that once mature that it will.
We do not recommend that users install this release except for testing and evaluation.
Big thanks to @keraion, who's been leading the way on this effort.
Additionally in this release:
These will be added to the changelog properly in the full 4.0.0 release.
This is an alpha release of SQLFluff 4.0 to begin verification of the rust portions of the codebase. In particular to verify that publishing to pypi w
This is an alpha release of SQLFluff 4.0 to begin verification of the rust portions of the codebase. In particular to verify that publishing to pypi works as expected, and that users can install the package. Rust support is still in beta, but from this release, users can install sqlfluff[rs] to get some of the parser running in rust. Current implementation is not expected to yield significant gains but we do expect that once mature that it will.
We do not recommend that users install this release except for testing and evaluation.
Big thanks to @keraion, who's been leading the way on this effort.
Additionally in this release:
These will be added to the changelog properly in the full 4.0.0 release.
Rule AM09: Handle ambiguous LIMIT/OFFSET without ORDER BY (non-deterministic results)
This release has 95 contributions in it!
Also, welcome to the twenty three new contributors! Thanks for your contributions!
ALTER DYNAMIC TABLE support (#7176) @keraionescape_replacements control character value (#7165) @keraion.sqlfluffignore when using stdin-filename (#7168) @keraionLIMIT or OFFSET without ORDER BY (non-deterministic results) (#6749) @d33bsDROP COLLATION statement (#7143) @keraionCOLUMN_VALUE as a bare function (#7144) @keraionpartitioned by and cluster by segments to SparkSQL Create view statement (#7137) @KikeSenpaiSTORING segment in BigQuery CREATE VECTOR INDEX (#7119) @agkphysicsDELTA to non-reserved keyword (#7031) @keraionALTER INDEX statements (#7046) @saulotoledoSELECT INTO (#7033) @keraionframe_clause to support all interval_expressions (#7034) @keraionCREATE NETWORK RULE statement (#7035) @keraionCREATE DATABASE syntax (#7055) @manmartgarcALTER TABLE ... RENAME CONSTRAINT (#7045) @saulotoledoCLUSTER BY clause (#7021) @keraionEXCEPTION WHEN clauses (#7018) @keraionSET tuple with a single expression (#7019) @keraionINVISIBLE/VISIBLE column constraints (#7020) @keraionENCODE for ALTER TABLE ADD COLUMN (#7022) @keraionALTER COLUMN clause (#7026) @keraioncolumn_properties (#7027) @keraionRELIES_ON and POLYMORPHIC keywords (#7015) @keraionLIMIT when not a limit clause (#7010) @keraionThis release adds support for two new dialects: _Apache Doris_ and _FlinkSQL_.
This release has 25 contributions in it!
Also, welcome to the five new contributors! Thanks for your contributions!
NO_COLOR environment variable (#6976) @keraionACTION a non-reserved keyword (#6970) @keraionjson_object syntax in Oracle. (#6973) @joaostorrerINSERT statements (#6955) @keraionThis is primarily a bugfix, rule enhancement, and dialect enhancement release.
This release has 80 contributions in it!
Also, welcome to the fourteen new contributors! Thanks for your contributions!
RETURNING INTO clause in INSERT, UPDATE, DELETE and MERGE statements in Oracle. (#6941) @joaostorrerUSER (bare function) unparsable (#6935) @keen85SECURITY POLICY (CREATE, ALTER, DROP) (#6937) @keen85IF statements and :NEW. variables in assignment statements in Oracle. (#6930) @joaostorrer<=> operator in MySQL. (#6929) @joaostorrer--stdin-filename (#6900) @keraion--disregard-sqlfluffignores for fix and format (#6885) @keraionSET statements in MySQL. (#6922) @joaostorrerLOAD_UNCERTAIN_FILES (#6879) @mxr/ operator. (#6853) @joaostorrerREMOVE DUPLICATES clause in merge statements in Redshift (#6841) @joaostorrerselect exclude syntax (#6838) @pierrandThis release brings a couple of breaking changes:
This release brings a couple of breaking changes:
LT15 (layout.newlines). This rule allows you to control the number of consecutive
blank lines both inside, and outside of queries.We also have a host of dialect improvements, bugfixes, and general code clean-up. This release has 79 contributions in it!
Also, welcome to the thirteen new contributors! Thanks for your contributions!
ZEROFILL columns in MySQL. (#6735) @joaostorrerCREATE TABLE statements in Redshift. (#6808) @joaostorrerCREATE USER statements in Oracle. (#6809) @joaostorrervarchar(max) in Redshift. (#6806) @joaostorrerAS not optional (#6780) @keraion+=, -=, *=, /= and %= operators in tsql. (#6756) @joaostorrerFixPatch ordering conflict (#6769) @keraionCREATE TABLE and ALTER TABLE statements in Oracle. (#6767) @joaostorrerPivotSegment to accept alias in FunctionSegment in Oracle. (#6766) @joaostorrerON CONFLICT indentation for Postgres (#6660) @WillMatthewsUNNEST (#6757) @keraioncreate user rsa_public_key=... / snowflake (#6731) @juli4nb4dilloALTER TABLE statements in MySQL. (#6742) @joaostorrerSTRUCT datatype (#6739) @NormallyGaussianUSER from reserved words in Postgres. (#6707) @joaostorrerkey: value syntax in functions in Postgres. (#6708) @joaostorrerDROP DYNAMIC TABLE (#6673) @LoganPrice344ALTER TABLE Parsing (#6654) @LoganPrice344CREATE AUTHENTICATION POLICY Parsing (#6685) @LoganPrice344JoinClauseSegment in DeleteStatementSegment in Postgres (#6692) @joaostorrerALTER TABLE statements in Oracle. (#6661) @joaostorrerDEFAULT keyword as function parameter in tsql. (#6663) @joaostorrerDECLARE Syntax (#6665) @LoganPrice344noqa (#6668) @keraionALTER TABLE Parsing (#6671) @LoganPrice344CREATE ROW ACCESS POLICY to Parse Quoted Policy Names (#6648) @LoganPrice344EVENT statements in MySQL. (#6646) @joaostorrerException Parsing (#6645) @LoganPrice344WithCompoundStatementSegment in procedures in Postgres (#6632) @joaostorrerSET NEW.<column> statements in MySQL. (#6634) @joaostorrerThis is a bugfix release resolving a several issues from 3.3.0 and previously.
This is a bugfix release resolving a several issues from 3.3.0 and previously.
This release also includes the first contributions from thirteen new contributors! Welcome to the project and thank you for your contributions. 🎉🎉🏆🏆🎉🎉
CREATE Syntax Parsing (#6514) @LoganPrice344geometry(point) datatype. (#6543) @joaostorrerSnowflake Target_lag (#6567) @LoganPrice344set_clause_list to UPDATE statement (#6605) @keraionNOMAXVALUE and NOMINVALUE (#6606) @keraionLOAD DATA statement (#6612) @VMois\gset and \gexec meta commands. (#6555) @joaostorrerALTER FOREIGN TABLE statement. (#6597) @joaostorrer&. (#6573) @joaostorrerWITH ROLLUP option for GROUP BY (#6579) @keraionlt_eq_gt operator (#6592) @keraionCREATE OPERATOR syntax. (#6540) @joaostorrerDROP FOREIGN TABLE statement. (#6548) @joaostorrer!!. (#6541) @joaostorrerALTER TAG Syntax (#6531) @LoganPrice344CREATE ROW ACCESS POLICY Syntax Parsing (#6550) @LoganPrice344ALTER_TABLE_COLUMN Syntax Parsing (#6526) @LoganPrice344ALTER ROW ACCESS POLICY Syntax Parsing (#6534) @LoganPrice344ALTER warehouse Syntax (#6516) @LoganPrice344GRANT syntax (#6520) @LoganPrice344GRANT command parsing (#6503) @korverdevCREATE OR ALTER syntax (#6497) @korverdevThis release brings a few more significant changes. Especially given the introduction of several new rules, we highly recommend testing this release o
This release brings a few more significant changes. Especially given the introduction of several new rules, we highly recommend testing this release on your project before upgrading to make sure they are configured appropriately for your project style guide. As always, we have tried to make sure that the defaults for all new rules are both widely applicable, and fairly light touch. While all have been tested on some existing larger codebases which the maintainers have access to - do still report any bugs you might find on GitHub in the usual manner.
appdirs package as a dependency (as an abandoned project) and instead added platformdirs instead. Users should not notice any functionality changes beyond the different dependency.AM08 (ambiguous.join_condition), which detects JOIN clauses without conditions (i.e. without an ON or USING clause). These are often typos and can result in significant row count increases if unintended.CV12 (convention.join_condition), which is related to AM08 and detects cases where users have used a WHERE clause instead of a JOIN ... ON ... clause to do their join conditions. The join condition is a form of metadata and should communicate to the end user how the table should be joined. By mixing this information into the WHERE clause it makes the SQL harder to understand.LT14 (layout.keyword_newline), which allows certain keywords to trigger line breaks in queries. Primarily this forces the main SELECT statement clauses like WHERE, GROUP BY etc. onto new lines. This rule has been designed to be highly configurable, but with sensible light-touch defaults. Check out the docs to adapt it to the conventions of your project.ST10 (structure.constant_expression), some SQL users include redundant expressions in their code (e.g. WHERE tbl.col = tbl.col). These conditions always evaluate to a constant outcome (i.e. always evaluate as TRUE or FALSE) as so add no functionality or meaning to the query. This rule catches them.ST11 (structure.unused_join), which detects unused joins in SQL statements, and is designed to catch tables that were once used, but where the column references have since been removed and now the table is unnecessary.Beyond these changes, we've seen a whole host of dialect improvements to almost all of the supported dialects and several bugfixes which are combined into this release.
We also welcome TWELVE new contributors to the project in this release. Thanks to all of them for their hard work 🚀🏆🚀.
appdirs to platformdirs (#6399) @alanmcruickshankNEXT VALUE FOR use as expression (#6431) @timz-stPARTITION_TYPE for CREATE EXTERNAL TABLE (#6422) @ninazacharia-toastfix command with --show-lint-violations (#6382) @joaopamaralTYPE property to Snowflake users (#6411) @mroy-seedboxCREATE VIRTUAL TABLE Statement (#6406) @R3gardlessThis release is mostly bugfixes and dialect improvements. Notably:
This release is mostly bugfixes and dialect improvements. Notably:
LT01 & LT02.AL09.AM02 for Trino and Snowflake.ST02 & LT01.There's also a bunch of documentation improvements in this release, including guides on how to troubleshoot SQLFluff and how to write custom rules. Check out https://docs.sqlfluff.com for more details.
We also saw five new contributors to the project this month. Welcome to the project, and thanks for taking the time to contribute! 🎉🏆🎉
IN functions (#6393) @keraionmatch_condition to touch (#6395) @keraionCONNECT BY expressions that may use PRIOR (#6396) @keraionALTER DATABASE SET (#6376) @keraionALTER AGGREGATE Statement (#6353) @R3gardlessRelationEmulator safely callable (#6358) @mroy-seedboxHandle deprecation warning of "fork" (#6332) @alanmcruickshank
This release is almost all dialect fixes and bugfixes. Notably also, this release brings official python 3.13 support too (although most users should not realise any differences).
We also see two new contributors to the project. Welcome @R3gardless & @brandonschabell! 🎉🎉🎉
DROP COLUMN support for multiple dialects (#6348) @keraionUPDATE to be a function name (#6349) @keraionreference_constraint (#6346) @keraiontox command in test/fixtures/dialects/README.md (#6342) @R3gardlessCREATE FOREIGN DATA WRAPPER statement (#6335) @keraionjson_query functions (#6336) @keraionThis is another release of dialect improvements and rule bugfixes. Notably:
This is another release of dialect improvements and rule bugfixes. Notably:
LT02.github-annotation-native format option now has groups for each filename.There's also a refactor of where we guides and howtos in the docs. Keep an eye on that section going forward for more information about best practice and troubleshooting for SQLFluff.
Even in this small PR, we've seen two new contributors. Welcome @nspcc-cm & @rogalski to the project!
UPDATE and RETURNING clauses (#6314) @keraiongrant monitor on user ... in Snowflake dialect (#6322) @mroy-seedboxgithub-annotation-native format option. (#6312) @alanmcruickshankThis is a hotfix release to resolve an issue with the JJ01 rule when running in parallel mode.
This is a hotfix release to resolve an issue with the JJ01 rule when running in parallel mode.
This release is primarily housekeeping, bugfixes and dialect improvements. More specifically:
This release is primarily housekeeping, bugfixes and dialect improvements. More specifically:
JJ01, filename extension handling and the treatment of unfixable/unparsable files, which have been noticed with recent releases.LT07 & LT12 which relate to jinja whitespace control.ref and source macros for the dbt templater.There's also dialect improvements for BigQuery, TSQL, MySQL, MariaDB, Snowflake, DuckDB, Databricks, Postgres, Teradata, Exasol & Vertica.
We also saw six new contributors merge their first pull request as part of this release. Welcome to the project! 🎉🏆🎉
DECLARE variables in BigQuery (#6295) @keraionThisEmulator (#6254) @mroy-seedboxtable_aliases option (#6273) @keraionEXECUTE IMMEDIATE (#6287) @keraionSET with system variables (#6288) @keraionpyproject.toml (#6286) @keraionGROUPING SETS clause (#6275) @keraionARRAY types (#6272) @keraionsqlfluff.core (#6246) @alanmcruickshankDROP MACRO (#6270) @keraionpyproject.toml nits (#6268) @alanmcruickshankutil up to strict typing (#6263) @alanmcruickshanksqlfluff.core.linter (#6240) @alanmcruickshankDatatypeSegment references (#6244) @keraionSET with double quoted identifiers (#6243) @keraionThis release brings a few minor breaking changes, both for the core project and for the dbt templater. For the main project:
This release brings a few minor breaking changes, both for the core project and for the dbt templater. For the main project:
Resolving an issue with the spacing of functions (LT01), which involved a change to how functions are parsed. If your project relies on the specific parsing of functions, the bracketed arguments are now wrapped in a function_contents object. We recommend that you examine the new parsing structure using this new release in testing first.
RF06 (references.quoting) is now case sensitive when removing quotes which are detected as unnecessary. This rule has also been re-enabled by default for Snowflake and Postgres where it had previously been disabled (for the reason that in the past it hadn't been appropriately case sensitive). Treatment for totally case-insensitive dialects like DuckDB and SparkSQL have also been included. Please check the new documentation for this rule (which is much more explicit now), for details related to your dialect.
Patterns equivalent to those from .sqlfluffignore can now be included in .sqlfluff and pyproject.toml files.
Using the python templater, users now have an option to include variables which include a dot in the path, like {{ foo.bar }} using a special sqlfluff context variable.
Significant changes under the hood to the handling of configuration files. Most of these should not be visible to end users, but for anyone integrating SQLFluff into a larger project and relying on native file loading may need to refactor their project for this release. Most notably here, for maintainers of plugins, the ConfigLoader class has been deprecated, and plugins should instead call the config loading functions directly. See the example plugin for details.
Documentation, especially for dialects, has been significantly improved. Documentation for CP02 (capitalisation.identifiers) has also been clarified to make it's implication for references and aliases more clear.
During testing, to isolate the effect of specific rules, there's a new CLI option --disable-noqa-except which allows all noqa options to be ignored except the ones provided in this option.
For the dbt templater:
Support for dbt 1.1-1.3 has been removed. All have been in End of Life (EOL) support by dbtlabs for almost two years. They are also poorly supported by other projects and tools.
The dbt templater has been migrated to use pyproject.toml.
Handling of errors and exceptions raised within dbt has had an overhaul. Users may see a slightly different presentation of errors, but the overall stability should be more robust.
In addition to those changes, there have been too many dialect contributions and bugfixes to mention specifically. We've also seen six people make their first contributions to the project as part of preparing for this release! 🎉🏆🎉.
config and helpers. (#6206) @alanmcruickshankSET statement (#6205) @keraionCREATE TYPE statement (#6204) @keraionCOMMENT ON statement (#6196) @keraionSTRUCT datatype (#6198) @keraionConfigLoader (#6177) @alanmcruickshankCREATE MACRO/CREATE FUNCTION (#6194) @keraionVARIANT type (#6167) @keraionINSERT OVERWRITE after a CTE (#6172) @keraionSET CONSTRAINTS statement (#6171) @keraionMERGE without a target alias (#6170) @keraionOFFSET and FETCH (#6169) @keraionSUBSCRIPTION statements (#6168) @keraionutil.py for dbt templater pyproject.toml (#6160) @keraionDISTINCTs with subqueries (#6146) @keraionENCRYPTED PASSWORD option in CREATE USER (#6143) @keraionINTERVALs to Frame Clause (#6105) @keraionIS UNKNOWN (#6094) @keraionThis release brings a bumper lot of bugfixes, dialect improvements and other minor improvements across the board. Most notably:
This release brings a bumper lot of bugfixes, dialect improvements and other minor improvements across the board. Most notably:
conf.py file in the docs folder for a full list of permalinks.markupsafe, ruamel.yaml, pydantic & rich.We've also seen fifteen new contributors to the project! Thanks to all of them for taking the time to contribute. 🎉🎉🏆🎉🎉
dbt deps test fixture timeout (#6088) @keraionWITH clauses (#6017) @keraionThis minor release has two breaking changes:
This minor release has two breaking changes:
This release also brings in support for the MariaDB dialect. As well as this, there are many bugfixes, and dialect improvements.
Thanks also to the twelve new contributors whose work was included in this release! 🎉🎉🏆🎉🎉
placeholder templater #5880 @fvankriekenThis is primarily a fix for compatibility with dbt 1.8+. Beyond that it also brings several dialect improvements to SQLite, Bigquery, MySQL, Oracle &
This is primarily a fix for compatibility with dbt 1.8+. Beyond that it also brings several dialect improvements to SQLite, Bigquery, MySQL, Oracle & Clickhouse.
Thanks also to the five new contributors whose work was included in this release! 🎉🎉🏆🎉🎉
This release primarily fixes an issue introduced by the recent dbt 1.7.14 release, and better support for dbt 1.7+. It also includes a range of dialec
This release primarily fixes an issue introduced by the recent dbt 1.7.14 release, and better support for dbt 1.7+. It also includes a range of dialect improvements and CLI refinements.
This release also includes the groundwork for linting the unrendered sections of Jinja templates. More documentation on this will be released in due course when it's ready for beta testing.
Thanks also to @padraic00 & @burhanyasar who made their first contributions in this release. 🎉🎉🏆🎉🎉
ALTER TABLE ... SWITCH PARTITION (#5807) @keen85--stdin-filename option (#5805) @keraionCREATE/ALTER/DROP MASTER KEY (#5802) @keen85CREATE/ALTER PARTITION FUNCTION/SCHEME (#5793) @keen85This release contains one larger change, which is a big upgrade to case sensitivity in the alias use rules. Also allowing the customisation of how SQL
This release contains one larger change, which is a big upgrade to case sensitivity in the alias use rules. Also allowing the customisation of how SQLFluff uses case sensitivity in rules like AL05. Beyond that, this also includes a handful of dialect improvements.
Thanks especially to @olshak, @MarkPaulin, @mhoogendoorn & @kawashiro who made their first contributions in this release! 🚀
This is a standard bugfix release bringing a bunch of dialect improvements and bugfixes. Almost every dialect sees some improvements and it also inclu
This is a standard bugfix release bringing a bunch of dialect improvements and bugfixes. Almost every dialect sees some improvements and it also includes quality of life improvements to the CLI, pre-commit hooks, docs and several rules.
Thanks also to the eight new contributors whose first contributions are included in this release. 🎉🎉🏆🎉🎉
CASE (#5753) @keraionGLOB, MATCH. Improved REGEXP (#5745) @keraion--force flag from pre-commit hook definition (#5739) @borcheroCASEs with different expressions (#5735) @keraionifNotExistsGrammar to Snowflake procedure (#5709) @IliyanKostov9This is a standard minor release fixing a set of dialect issues with Trino, BigQuery, Vertica and Snowflake.
This is a standard minor release fixing a set of dialect issues with Trino, BigQuery, Vertica and Snowflake.
Thanks to @maegan-canva, @rileymcdowell & @paysni who made their first contributions in this release.
This is primarily another hotfix release for 3.0.0. Specifically making sure the deprecation warnings for -f/--force go to stderr rather than stdout.…
This is primarily another hotfix release for 3.0.0. Specifically making sure the deprecation warnings for -f/--force go to stderr rather than stdout. It also includes two dialect improvements, one for Snowflake and one for T-SQL.
--force deprecation print on stderr #5681 @keraionThis minor release is a hotfix to resolve a bug introduced affecting CLI exit codes in the 3.0.0 release.
This minor release is a hotfix to resolve a bug introduced affecting CLI exit codes in the 3.0.0 release.
This release brings several breaking changes to previous releases. Most notably:
This release brings several breaking changes to previous releases. Most notably:
It drops support for python 3.7, which reached end of life in June 2023.
It migrates to pyproject.toml rather than setup.cfg as the python packaging configuration file (although keeping setuptools as the default backend).
The serialised output for sqlfluff lint (and the corresponding API methods) now contains more information about the span of linting issues, initial proposed fixes and several statistics which were previously only accessible via csv export. Beside the new fields, the original fields of line_pos and line_no have been renamed to start_line_pos and start_line_no, to distinguish them from the new fields starting end_*.
The default annotation_level set by the --annotation-level option on the sqlfluff lint command has been changed from notice to warning, to better distinguish linting errors from warnings, which always now have the level of notice. This is only relevant when using the github-annotation or github-annotation-native formats.
A change in the default behaviour for convention.not_equals. The new default is to be consistent, which is slightly more relaxed than the original behaviour.
The --force option has been deprecated on sqlfluff fix as that option is now the default behaviour. This is to enable significant reductions in memory overhead when linting large projects.
The long since deprecated --disable_progress_bar option has been removed (which was replaced by the kabab-case --disable-progress-bar more than a year ago).
Plugins are now loaded progressively, and with error handling. If a plugin fails to load, SQLFluff will now continue onward and try to run regardless while also showing a more helpful error message.
On top of these changes, there have a been a whole host of dialect improvements and additions, in particular the inclusion of avertica dialect for the first time. There's also:
A new rule (aliasing.self_alias.column) which prevents aliasing a column as itself.
A change to disables AL01 (aliasing.table) by default for Oracle.
A change to allow AL05 to allow aliasing for a VALUES clause.
For more specifics please take a look at the release notes.
Thanks to the community for patience during the release cycle for 3.0.0, which has taken a little longer than expected. Thanks also to the TWENTY SEVEN new contributors whose changes are included in this release. 🎉🎉🏆🎉🎉
CREATE FUNCTION Syntax in SparkSQL Parser #5615 @mitchellvanrijkom--force for --check #5650 @alanmcruickshankDeprecatedOption #5649 @alanmcruickshank_code_indices in `BaseSegment::raw_segmen… #5644 @gvozdvmozguDISTINCT FROM optional; SQLite/TSQL/Exasol: Nothing'd NanLiteralSegment #5620 @keraionLATERAL VIEW following JOIN; CLUSTER|SORT|DISTRIBUTE BY or QUALIFY without FROM #5602 @keraionno_implicit_reexport mypy check #5509 @KoyaaniEXCEPT with qualified column reference #5557 @keraionREPLACE after EXCLUDE. Fix AL03 linting for wildcard like expression. #5556 @keraionGLOBAL JOIN, GLOBAL IN, and PASTE JOIN #5560 @keraionLATERAL. #5533 @keraionUNPIVOT syntax. Fix TABLESAMPLE aliases. #5524 @keraionPIVOT and UNPIVOT #5514 @keraionDECLARE GLOBAL TEMPORARY TABLES, OFFSET, CALL, and non-bracketed VALUES #5508 @keraiontest__api__lint_string_specific_exclude_single #5437 @gvozdvmozgupyproject.toml #5383 @alanmcruickshankpyproject.toml for the core project. #5373 @alanmcruickshank…large projects. As part of that we've also deprecated the --force option on sqlfluff fix and made that the default behaviour (the associated memory op…
This introduces some memory optimisations in the linting operation which prevent a major cause of crashes when linting large projects. As part of that we've also deprecated the --force option on sqlfluff fix and made that the default behaviour (the associated memory optimisations will come shortly).
This also removes the long since deprecated --disable_progress_bar option (which was replaced by the kabab-case --disable-progress -bar more than a year ago).
On top of that this release also introduces the vertica dialect for the first time, and a whole host of bugfixes and improvements to other dialects.
This release should be considered a release candidate for the final 3.0.0 release which will follow shortly in the next few days unless any other major issues are found.
Thanks particularly to the seven new contributors we saw in this release 🏆🎉.
CREATE FUNCTION Syntax in SparkSQL Parser (#5615) @mitchellvanrijkom--force for --check (#5650) @alanmcruickshankDeprecatedOption (#5649) @alanmcruickshank_code_indices in `BaseSegment::raw_segmen… (#5644) @gvozdvmozguDISTINCT FROM optional; SQLite/TSQL/Exasol: Nothing'd NanLiteralSegment (#5620) @keraionLATERAL VIEW following JOIN; CLUSTER|SORT|DISTRIBUTE BY or QUALIFY without FROM (#5602) @keraionno_implicit_reexport mypy check (#5509) @KoyaaniThis release primarily brings through a large set of dialect improvements and bugfixes from over the holiday period. Notably also:
This release primarily brings through a large set of dialect improvements and bugfixes from over the holiday period. Notably also:
convention.not_equals. The new default is to be consistent, which is slightly more relaxed than the original behaviour.aliasing.self_alias.column) which prevents aliasing a column as itself.AL01 (aliasing.table) by default for Oracle.This release also saw ELEVEN new contributors in this release 🎉🎉🏆🏆🎉🎉. Great to see so many new people getting involved with the project. Thank You 🙏.
EXCEPT with qualified column reference #5557 @keraionREPLACE after EXCLUDE. Fix AL03 linting for wildcard like expression. #5556 @keraionGLOBAL JOIN, GLOBAL IN, and PASTE JOIN #5560 @keraionLATERAL. #5533 @keraionUNPIVOT syntax. Fix TABLESAMPLE aliases. #5524 @keraionPIVOT and UNPIVOT #5514 @keraionDECLARE GLOBAL TEMPORARY TABLES, OFFSET, CALL, and non-bracketed VALUES #5508 @keraionThis release makes a breaking change to the serialized output of the CLI (and by extension, any of the serialized outputs of the API).
This release makes a breaking change to the serialized output of the CLI (and by extension, any of the serialized outputs of the API).
The serialised output for sqlfluff lint now contains more information about the span of linting issues and initial proposed fixes. Beside the new fields, the original fields of line_pos and line_no have been renamed to start_line_pos and start_line_no, to distinguish them from the new fields starting end_*.
The default annotation_level set by the --annotation-level option on the sqlfluff lint command has been changed from notice to warning, to better distinguish linting errors from warnings, which always now have the level of notice. This is only relevant when using the github-annotation or github-annotation-native formats.
…the more minor fixes flowing through while other breaking changes are staged in. In particular there are a few dialect improvements for Snowflake, TSQ…
This brings no further breaking changes on top of 3.0.0a2, but instead releases a few of the more minor fixes flowing through while other breaking changes are staged in. In particular there are a few dialect improvements for Snowflake, TSQL, SQLite and Databricks alongside a few further improvements to deployment scripts off the back of earlier changes for 3.x.
test__api__lint_string_specific_exclude_single #5437 @gvozdvmozguThe initial 3.0.0a1 release failed to build a docker image, this resolves that issue.
The initial 3.0.0a1 release failed to build a docker image, this resolves that issue.
This release makes a couple of potentially breaking changes:
This release makes a couple of potentially breaking changes:
It drops support for python 3.7, which reached end of life in June 2023.
It migrates to pyproject.toml rather than setup.cfg as the python packaging configuration file (although keeping setuptools as the default backend).
Further breaking changes may be made as part of the full 3.0.0 release, but this alpha release is designed to test the new packaging changes for any issues before releasing a stable version.
pyproject.toml #5383 @alanmcruickshankpyproject.toml for the core project. #5373 @alanmcruickshankThis is a fairly minor release, primarily bugfixes and dialect improvements.
This is a fairly minor release, primarily bugfixes and dialect improvements.
For python API users, there's the addition of a public method on the FluffConfig object allowing the construction of a config object from multiple strings to mimic the effect of nested config files in the CLI.
This release also includes a selection of internal refactoring and reorganisation to support future development work.
This also sees the first contributions by @ShubhamJagtap2000 & @kang8, particularly notable in that both were contributions to SQLFluff documentation! 🎉🎉🏆🎉🎉
sqlfluff.core #5348 @alanmcruickshankRawFileSlice #5338 @alanmcruickshankBEGIN..EXCEPTION..END #5322 @abdelThis is a fairly small bugfix release, mostly to resolve a bug introduced in 2.3.3 with commas and LT09. This also includes a couple of additional sma
This is a fairly small bugfix release, mostly to resolve a bug introduced in 2.3.3 with commas and LT09. This also includes a couple of additional small performance improvements and some dialect improvements for Oracle, BigQuery and MySQL.
Thanks in particular to @bonnal-enzo who made their first contribution as part of this release 🎉🎉🏆🎉🎉.
Set to FrozenSet in segment class_types #5334 @alanmcruickshankThere's a *lot* in this release. Most of it is under the covers and so shouldn't cause any breaking changes for most users. If your use case depends o…
There's a lot in this release. Most of it is under the covers and so shouldn't cause any breaking changes for most users. If your use case depends on some of the internals of SQLFluff, you may find some breaking changes. The bigger changes are:
.match() methods, and also removes the parse_grammar attribute on any dialect segments. We are not aware of any 3rd party libraries which rely on these APIs however and so have not triggered a more major release. These lead to significant performance improvements during parsing.ParseMode option has enabled the removal of the StartsWith, GreedyUntil and EphemeralSegment parser classes.Alongside the big things this also includes a host of bugfixes, dialect improvements and CI/testing improvements.
This release also sees a bumper crop of new contributors, thanks to @dehume, @andychannery, @Kylea650, @robin-alphasophia, @jtbg, @r-petit, @bpfaust, @freewaydev & @abdel who all made the first contibutions in this release! 🎉🎉🎉
BaseSegment hash in reflow #5320 @alanmcruickshankBEGIN..EXCEPTION...END block #5307 @abdel_process_lint_result #5304 @alanmcruickshankHISTORY_RETENTION_PERIOD sequence to the table option segment #5273 @r-petitGreedyUntil #5263 @alanmcruickshanktype to instance_types #5253 @alanmcruickshankparse_grammar #5189 @alanmcruickshankBaseSegment.copy() isolation #5206 @alanmcruickshankAnything() + Strip most of the other parse_grammar #5186 @alanmcruickshankAnyNumberOf #5187 @alanmcruickshankparse_mode and remove StartsWith & EphemeralSegment. #5167 @alanmcruickshankMuch of this release is internal optimisations and refactoring. We're in the process of upgrading some quite old code in the parser, most of which sho
Much of this release is internal optimisations and refactoring. We're in the process of upgrading some quite old code in the parser, most of which should not be visible to end users (apart from perhaps some performance improvements!).
This release also allows missing template variables in the placeholder templater to be automatically filled with the name of the variable rather than raising an error (see: #5101).
Beyond that this includes some dialect improvements for DuckDB, SparkSQL, Snowflake, Redshift & Postgres.
Thanks particularly to @shyaginuma, @Fullcure3, @adilkhanekt & @pilou-komoot who made their first contributions as part of this release. 🎉🎉🎉
enforce_whitespace_preceding_terminator #5162 @alanmcruickshankDelimited #5161 @alanmcruickshankterminator > terminators on StartsWith #5152 @alanmcruickshankterminator > terminators on Delimited grammar #5150 @alanmcruickshankThis release is primarily a performance release, with most major changes aimed at the linting and fixing phases of operation. Most of the longest dura
This release is primarily a performance release, with most major changes aimed at the linting and fixing phases of operation. Most of the longest duration rules (excepting the layout rules) should see noticeable speed improvements.
Alongside those changes, there are a selection of bugfixes and dialect improvements for Oracle, PostgreSQL, Snowflake & TSQL.
fix) #5119 @alanmcruickshankEXCEPT #5126 @ulixius9This release brings one new dialect, two new rules and some changes to the CLI:
This release brings one new dialect, two new rules and some changes to the CLI:
ST09 / structure.join_condition_order: Which checks whether tables referenced in JOIN clauses are referenced in the order of their definition. By default this means that in the ON clause, the column referencing the table in the FROM clause should come before the column referencing the table in the JOIN clause (e.g. ... FROM a JOIN b on a.c = b.c). This rule was also the first contribution to the project from @thibonacci 🏆.AL08 / aliasing.unique.column: Which checks that column aliases and names are not repeated within the same SELECT clause. This is normally an error as it implies the same column has been imported twice, or that two expressions have been given the same alias.--profiler option on sqlfluff parse has been removed. It was only present on the parse command and not lint or fix, and it is just as simple to invoke the python cProfiler directly.--recurse cli option and sqlfluff.recurse configuration option have both been removed. They both existed purely for debugging the parser, and were never used in a production setting. The improvement in other debugging messages when unparsable sections are found means that this option is no longer necessary.Along side these more significant changes this also includes:
AL04, AL05, AM04, RF01 & ST05 which cumulatively may save up to 30% on the total time spend in the linting phase for some projects.This is primarily a bugfix release for 2.2.0 which introduced a bug in the exit_code returned by linting commands which ignored errors while setting p
This is primarily a bugfix release for 2.2.0 which introduced a bug in the exit_code returned by linting commands which ignored errors while setting processes > 1.
In addition to that this release introduces bugfixes for:
dbt exceptions.-f yaml or -f json alongside the dbt templater.This also introduces dialect improvements for Oracle and for LIMIT clauses.
Thanks also to @adityapat3l who made their first contribution as part of this release! 🎉🎉🎉
_prune_options within _longest_trimmed_match. #5063 @alanmcruickshankThis release changes some of the interfaces between SQLFluff core and our plugin ecosystem. The only *breaking* change is in the interface between SQL
This release changes some of the interfaces between SQLFluff core and our plugin ecosystem. The only breaking change is in the interface between SQLFluff and templater plugins (which are not common in the ecosystem, hence why this is only a minor and not a major release).
For all plugins, we also recommend a different structure for their imports (especially for rule plugins which are more common in the ecosystem) - for performance and stability reasons. Some users had been experiencing very long import times with previous releases as a result of the layout of plugin imports. Users with affected plugins will begin to see a warning from this release onward, which can be resolved for their plugin by updating to a new version of that plugin which follows the guidelines.
For more details (especially if you're a plugin maintainer) see our release notes.
Additionally this release includes:
FluffConfig object directly, and better support for parsing config files directly from strings (see the included example).AM06.--warn-unused-ignores CLI option (and corresponding config setting) to allow warnings to be shown if any noqa comments in SQL files are unused.Thanks also to @kaiyannameighu, @josef-v, @aglebov & @joaostorrer who made their first contributions as part of this release! 🎉🎉🎉
ADD COLUMN IF NOT EXISTS syntax on ALTER TABLE #5035 @wfelipewnoqa directives #5029 @alanmcruickshankmake_template to render_func in jinja and dbt #4942 @alanmcruickshank…both their layout rules and for any removed or deprecated settings.
This release brings some meaningful performance improvements to the parsing of complex SQL statements. In files with deeply nested expressions, we have seen up to a 50% reduction on time spent in the parsing phase. These changes are all internal optimisations and have minimal implications for the parser. In a few isolated cases they did highlight inconsistencies in the parsing of literals and so if your use case relies on the specific structure of literal and expression parsing you may find some small differences in how some expressions are parsed.
Additionally this release brings new validation steps to configuration. Layout configuration is now validated on load (and so users with invalid layout configurations may see some of these being caught now) and inline configuration statements in files are also now validated for both their layout rules and for any removed or deprecated settings.
On top of both we've seen dialect improvements to Databricks, PostgreSQL, BigQuery, Snowflake & Athena.
CROSS JOIN syntax #4996 @tunethewebThis release is a fairly standard incremental release. Highlights include bugfixes to RF05 and dialect improvements to Snowflake, Teradata, MySQL, TSQ
This release is a fairly standard incremental release. Highlights include bugfixes to RF05 and dialect improvements to Snowflake, Teradata, MySQL, TSQL, SparkSQL & Postgres.
Internally, the last few weeks have brought several improvements to developer tooling.
We've also moved over to GitHub sponsorships - so if you previously used the old flattr link, you can find our new profile page at https://github.com/sponsors/sqlfluff.
…as the folks at dbt-labs have often backported breaking changes to their internal APIs to previous versions of dbt-core. This release does at least br…
This release resolves compatibility issues with a set of dbt-core versions.
dbt-core 1.5.2 onwards is now properly supported.dbt-core 1.1 to 1.4 has now been re-enabled after support had to be abandoned a few releases ago.NOTE: We cannot guarantee that SQLFluff will always continue to remain compatible with all dbt versions, particularly as the folks at dbt-labs have often backported breaking changes to their internal APIs to previous versions of dbt-core. This release does at least bring more extensive internal testing to catch when this does occur to allow our community to react.
This release fixes also resolves a potential security issue for when using external libraries (and the library_path config setting), and also contains various dialect improvements.
SQLFLUFF_JINJA_FILTERS #4932 @dmohnsDROP EXTERNAL TABLE #4919 @keen85$ and # in identifier #4903 @ulixius9profiles dir env var or default (#4886) @JasonGluck
struct in TO_JSON (#4879) @dimitris-flyrgroup by (#4869) @KulykDmytroCUBE ROLLUP GROUPING SETS (#4862) @KulykDmytroThis release brings support for dbt 1.5+. Some internals of dbt mean that SQFluff versions prior to this release may experience errors with dbt versio
This release brings support for dbt 1.5+. Some internals of dbt mean that SQFluff versions prior to this release may experience errors with dbt versions post 1.5. In addition to that there are some dialect and templating improvements bundled too:
CASE WHEN clauses.WHEN blocks and introduce indented_then_contents #4755 @borcheroThis is a bugfix release to resolve two regressions included in 2.0.6 related to implicit indents. This also includes a bugfix for config file on osx,
This is a bugfix release to resolve two regressions included in 2.0.6 related to implicit indents. This also includes a bugfix for config file on osx, contributed by first time contributor @jpuris 🎉.
Introduction of a --quiet option for the CLI for situations where less output is useful.
--quiet option for the CLI for situations where less output is useful.--force option is used for sqlfluff fix each file is fixed during the linting process rather than at the end.layout.end-of-file to layout.end_of_file in line with other rules.SAFE prefix segment (#4773) @dmohnsThis is a relatively swift bugfix to refine some of the changes made to widow function indentation in 2.0.4. In addition there are two dialect refinem
This is a relatively swift bugfix to refine some of the changes made to widow function indentation in 2.0.4. In addition there are two dialect refinements also made since that release.
This is primarily a _bugfix_ and _dialect_ release:
This is primarily a bugfix and dialect release:
--persist-timing option is now also available on sqlfluff fix.Thanks also to @james-johnston-thumbtack and @Thashin who made their first contributions in this release. In particular, @james-johnston-thumbtack made twenty one contributions in their first month! 🎉🎉🎉
fix too. #4679 @alanmcruickshankThis is primarily a _bugfix_ and _dialect_ release:
This is primarily a bugfix and dialect release:
THEN in CASE statements (see #4598).TypedParser, LT03 & LT04.--persist-timing option for deeper performance understanding.We also saw a huge number of first time contributors with 9 contributing in this release 🎉🏆🎉.
is_alias_required as a private class so it doesn't appear in docs #4673 @tunethewebOPENJSON() #4652 @keen85Create External Table #4642 @aly76MERGE INSERT clause #4666 @dmohnsCREATE EXTERNAL FILE FORMAT #4647 @keen85sqlcmd commands :r and :setvar #4653 @keen85PERIOD FOR SYSTEM_TIME (temporal tables) #4654 @keen85CREATE EXTERNAL DATA SOURCE #4634 @keen85WITH ORDINALITY clauses in Postgres #4599 @tunethewebThis is primarily a _bugfix_ release. Most notably this solves some of the issues introduced in 2.0.1 around spacing within datatypes. Expressions lik
This is primarily a bugfix release. Most notably this solves some of the issues introduced in 2.0.1 around spacing within datatypes. Expressions like 1.0::double precision should now be spaced correctly.
Beyond that, this contains a selection of smaller bugfixes and dialect improvements. Even for a relatively small release we saw three new contributors (thanks @aurany, @JackWolverson & @mikaeltw 🎉).
The one new feature (as such) is being able to now configure LT05 (aka layout.long_lines) to optionally move trailing comments after the line they are found on, rather than the default behaviour of moving them up and before. Users can enable this with the trailing_comments configuration setting in the indentation section.
This release also contains some performance optimisations in the parser, especially on queries with heavily nested expressions. There will be more to come in this space, but we hope this leads to a better experience for many users. 🚀
Github Action Deprecations (#4545) @alanmcruickshank
This is mostly a bugfix release addressing some of the issues from the recent 2.0 release. Notable fixes are:
LT01) for datatypes, hyphenated identifiers and casting operators.LT02), in particular with implicit indents.LT09 and LT02, by only limiting LT09 to bringing targets onto a single line if there is only one select target and that it contains no newlines.pyproject.toml.This release also brings one small new feature in allowing additional flags to be passed to SQLFluff when called as a pre-commit hook.
Thanks especially to @JavierMonton and @LauraRichter who made their first contributions to the project as part of this release! 🎉🏆
sqlfluff invocations in pre-commit hooks (#4546) @borcherocreate user statement (#4514) @JavierMontonUpgrading to 2.0 brings several important breaking changes:
Upgrading to 2.0 brings several important breaking changes:
L00X formats into groups within similar codes (e.g. an aliasing group with codes of the format AL0X), but also given names to allow much clearer referencing (e.g. aliasing.column).L001, L005, L006, L008, L023, L024, L039, L048 & L071 have been combined simply into LT01.1.1.To help users upgrade to 2.0, we've put together a recommended process as part of our release notes.
Beyond the breaking changes, this release brings a load of additional changes:
sqlfluff format CLI command (a la sqlfmt or black) to auto-format sql files using a known set of fairly safe rules.sparksql).As a new major release, especially with significant rewrites of large portions of the codebase, we recommend using compatible release specifiers in your dependencies (i.e. sqlfluff~=2.0.0) so that you can automatically take advantage of any bugfix releases in the coming weeks. The alpha releases of 2.0.0 have been tested on a range of large projects, but we know that the range of use cases "in the wild" is very diverse. If you do experience issues, please post them on GitHub in the usual manner.
Finally thanks to everyone who has worked on this release, especially @konnectr, @ValentinCrr, @FabianScheidt, @dflem97, @timcosta, @AidanHarveyNelson, @joar, @jmpfar, @jared-rimmer, @vesatoivonen, @briankravec, @saintamh, @tdurieux, @baa-ableton & @WillAyd who made their first contributions during the development of 2.0.0. Thanks for your contributions, and especially your patience in the slightly slower release of your efforts into the wild. 🙏🎉
UNPIVOT clauses #4494 @imrehgtoml dependency if < Python 3.11 (otherwise use builtin tomllib) #4303 @kevinmarsh> NOTE: This is effectively a release candidate for testing purposes. There are several new features here, and breaking changes to configuration. We w…
NOTE: This is effectively a release candidate for testing purposes. There are several new features here, and breaking changes to configuration. We welcome testing feedback from the community, and the intent is that following this release there will be no more major breaking changes in the before the 2.0.0 release.
This is the sixth alpha release for 2.0.0, and effectively the first release candidate for 2.0.0. All the intended breaking changes for the upcoming release have now been made and only bugfixes and non breaking feature changes should happen between this release and the full release.
It contains:
sqlfluff format CLI command (a la sqlfmt or black) to auto-format sql files using a known set of fairly safe set of rules.sparksql).There are also numerous dialect improvements to ANSI, Athena, TSQL, Teradata, SQLite & MySQL.
One column per quarter.