Skip to content

fix(layout): avoid LT01 false positives on postgres || in CASE ELSE#2497

Merged
benfdking merged 1 commit intomainfrom
fix/lt01-postgres-case-else-concat
Mar 30, 2026
Merged

fix(layout): avoid LT01 false positives on postgres || in CASE ELSE#2497
benfdking merged 1 commit intomainfrom
fix/lt01-postgres-case-else-concat

Conversation

@gvozdvmozgu
Copy link
Copy Markdown
Collaborator

fix #1251

@github-actions
Copy link
Copy Markdown
Contributor

Benchmark for 8969eac

Click to view benchmark
Test Base PR %
DepthMap::from_parent 49.4±2.73µs 48.7±0.56µs -1.42%
fix_complex_query 11.2±0.22ms 11.4±0.24ms +1.79%
fix_superlong 206.6±6.32ms 189.8±6.69ms -8.13%
parse_complex_query 4.5±0.08µs 4.6±0.07µs +2.22%
parse_expression_recursion 7.2±0.05µs 7.4±0.12µs +2.78%
parse_simple_query 962.8±20.03ns 1052.6±12.23ns +9.33%

@benfdking benfdking merged commit 8b33ce8 into main Mar 30, 2026
24 of 28 checks passed
@benfdking benfdking deleted the fix/lt01-postgres-case-else-concat branch March 30, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: LT01 is applied when ELSE clause contains ||

2 participants