fix(redshift): strip trailing semicolon on unlimited query path - #2482
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
Walkthrough
ChangesRedshift query normalization
Estimated code review effort: 2 (Simple) | ~5 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The shared CI failure here ( |
d81554b to
8fda05b
Compare
Summary
query()now strips a terminating semicolon/whitespace run even whenlimit is None.Motivation
Limited Redshift queries already subquery-wrap after stripping trailing
;. The unlimited path executed raw SQL, so client SQL ending with;could still fail depending on session/driver batching. Strip for both paths (string-literal-safe terminating-run regex already used by this connector).Verification
core/wren/.venv/bin/python -m pytest tests/unit/test_redshift_semicolon.py -q— 5 passedquery("SELECT 1;")sendsSELECT 1on the unlimited path.Apache path:
core/wren/**.Summary by CodeRabbit
;.