flowscope-core 0.7.0

Core SQL lineage analysis engine
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143

# Scoping and alias visibility rules for SQL dialects
# These rules determine where SELECT aliases can be referenced

[bigquery]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = true
# BigQuery expands aliases early, but has special handling for ambiguous cases

[clickhouse]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = true
# ClickHouse is permissive with alias references

[databricks]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = true
# Databricks follows Spark rules

[doris]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Using default rules for doris

[drill]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Using default rules for drill

[duckdb]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = true
# DuckDB is generally permissive like MySQL

[hive]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = true
# Hive follows Spark-like permissiveness

[mysql]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = false
# MySQL is permissive with alias references

[oracle]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Oracle is strict like PostgreSQL

[postgres]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# PostgreSQL is strict - must use expressions or ordinal positions

[presto]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Presto follows PostgreSQL-like strictness

[redshift]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = false
# Redshift is based on PostgreSQL but more permissive

[snowflake]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = true
# Snowflake only exposes SELECT aliases to ORDER BY (GROUP BY/HAVING still see raw expressions)

[spark]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = true
# Spark/Databricks support alias expansion

[sqlite]
alias_in_group_by = true
alias_in_having = true
alias_in_order_by = true
lateral_column_alias = false
# SQLite allows alias references in GROUP BY and HAVING
# Verified: SELECT x+y AS sum FROM (VALUES(1,2)) AS t(x,y) GROUP BY sum; works

[starrocks]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Using default rules for starrocks

[tableau]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Using default rules for tableau

[teradata]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Using default rules for teradata

[trino]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# Trino (Presto fork) follows same rules

[mssql]
alias_in_group_by = false
alias_in_having = false
alias_in_order_by = true
lateral_column_alias = false
# SQL Server is strict - must repeat expression