.sqlfluff

[sqlfluff]
templater = jinja
dialect = duckdb
sql_file_exts = .sql.j2,.sql
ignore = templating
runaway_limit = 10
max_line_length = 140

# Comma separated list of rules to exclude, or None
# See https://docs.sqlfluff.com/en/stable/perma/rule_disabling.html
# AM04 (ambiguous.column_count) and ST06 (structure.column_order) are
# two of the more controversial rules included to illustrate usage.
exclude_rules = structure.column_order, structure.using

[sqlfluff:indentation]
indented_joins = false
indented_using_on = true
template_blocks_indent = false
tab_space_size = 2

[sqlfluff:layout:type:comma]
line_position = leading

[sqlfluff:templater]
unwrap_wrapped_queries = true

[sqlfluff:templater:jinja]
apply_dbt_builtins = true

# The default configuration for capitalisation rules is "consistent"
# which will auto-detect the setting from the rest of the file. This
# is less desirable in a new project and you may find this (slightly
# more strict) setting more useful.
# Typically we find users rely on syntax highlighting rather than
# capitalisation to distinguish between keywords and identifiers.
# Clearly, if your organisation has already settled on uppercase
# formatting for any of these syntax elements then set them to "upper".
# See https://stackoverflow.com/questions/608196/why-should-i-capitalize-my-sql-keywords-is-there-a-good-reason
[sqlfluff:rules:capitalisation.keywords]
capitalisation_policy = upper

[sqlfluff:rules:capitalisation.identifiers]
capitalisation_policy = consistent
ignore_words = Date

[sqlfluff:rules:capitalisation.functions]
extended_capitalisation_policy = consistent
ignore_words = dateDiff

[sqlfluff:rules:capitalisation.literals]
capitalisation_policy = consistent

[sqlfluff:rules:capitalisation.types]
extended_capitalisation_policy = consistent
ignore_words =  DateTime,UInt64,FixedString