SQLFluff

SQL linter & auto-formatter for humans. BigQuery Db2 Exasol Hive MySQL Oracle Postgres Redshift Snowflake SQLite Teradata & T-SQL. Jinja & dbt templating.

[SQLFluff @SQLFluff]

@rp926463 We’ve an active Slack channel:

https://t.co/5igsoqMTyW

Bugs and feature requests are better tracked as GitHub issues. But can ask questions or seek advice on Slack. Or even get help in contributing to the code if willing— often the quickest way of getting your issues sorted!

[SQLFluff @SQLFluff]

@mariahjrogers Got some details? Could you raise an issue on GitHub? https://t.co/YSjzFYqyLA ?

[Robin Rump @RobinRump]

We deployed @SQLFluff in Alpha Sophia‘s code base this week - amazing workflow tool if you run SQL at scale and are used to static linting.

[SQLFluff @SQLFluff]

@WarrenTwasHere Have a read of this: https://t.co/2FWHnXPYFg

The default config (with all the default settings) is here: https://t.co/BM4RRoBjOi

Convention.coalesce is a rule name not a config option.

[Boaz Wasserman @BoazWasserman]

For working with LLM-generated SQL, I highly recommend using @SQLFluff to perform static analysis on the query to make sure it is both sematically correct and safe

https://t.co/UEU0C6kq0g

[Delta Lake @DeltaLakeOSS]

In the post, @LorinDawson explores how combining @SQLFluff's powerful #SQL linting capabilities with #DeltaLake's schema enforcement and constraints can significantly enhance your data pipelines and workflows. 🦀 https://t.co/8cTNPgnH2A

#opensource #data #oss #sqlfluff

[Khuyen Tran @KhuyenTran16]

With SQLFluff, you can automatically lint your SQL code and correct most linting errors.

SQLFluff supports various SQL dialects such as ANSI, MySQL, PostgreSQL, BigQuery, Databricks, Oracle, Teradata, etc.

Link to SQLFluff: https://t.co/snoQROsw9n

[SQLFluff @SQLFluff]

Unfortunately this upgrade does require some configuration changes so we wrote a migration guide here:

https://t.co/J6ZaKHLpkj

[SQLFluff @SQLFluff]

We recently released SQLFluff v2. This is a major upgrade including much better white space formatting and new rules naming convention.

https://t.co/IqokXaoi7s

[Hugh Cameron @HughCameron]

The upcoming @SQLFluff release will support the @duckdb dialect. What has #datatwitter been using for formatting so far?

[SQLFluff @SQLFluff]

We’ve also got a fantastic community on Slack to help you get started, so if you’ve a missing syntax or feature and wanna fix that, or have just been wanting to get into open source for a while, then the SQLFluff project is a great one to contribute to!

https://t.co/tfwj7povsY

[SQLFluff @SQLFluff]

SQLFluff currently has 314 open issues. That's up from around 100 last year. We ❤️ and need new contributors! 🎉

Docs for new contributors:
- https://t.co/5DAcovlNHN
- https://t.co/ZsAoiI4ylU

[SQLFluff @SQLFluff]

And if you’re still new and a little confused on Git, then we’ve a good guide on that too!

https://t.co/JaVjI5VYdZ

[Jonathan Bowman @jdbowman]

Using and exploring @SQLFluff for both linting and auto-formatting SQL. Very flexible and configurable. Honestly, can't find better in the open source space. Actively developed. https://t.co/aNB0iQY6Fv

[datacoves @datacoves]

We are proud to sponsor improvements to the #sqlfluff VS Code extension.

We are the now core contributors to the project and worked to fix some long-standing issues.

https://t.co/N6ODH3Kqd6

https://t.co/P1BoStqvnk

https://t.co/ApZyDY5GzG

[Joseph Machado @startdataeng]

SQL PRs getting slammed with nits about formatting? You can save time and prevent PR nits fatigue using an auto formatter!

Enter SQLFluff, a linter with functionality to support templating (in dbt) and multiple SQL variants (even SparkSQL).

#SQL #dataengineering

[Rugg @rd_rugg]

Have you ever had to interpret an unreadable SQL query?

Don't be that person.
Format with SQLFluff, a dialect-flexible and configurable SQL linter.

It supports:
ANSI SQL
Athena
BigQuery
Hive
MySQL
Oracle
PostgreSQL
Redshift
Snowflake
SparkSQL
SQLite
and more.
👇

[Michael Kahan @kahandata]

Nobody likes to feel dumb.

A teammate nit-picking your code can make you feel that way.

But it's important to stay consistent.

One solution: Implement a linter.

Two examples:
• @SQLFluff
• PyLint

Changes are less offensive when suggested by a computer.

[SQLFluff @SQLFluff]

@dbrtly_ @matsonj @ergestx Well actually… I think in this case you mean L012:

https://t.co/aRN6VA5tRj