Repository navigation
Drop CREATE FOREIGN TABLE with a foreign data warning - #106
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Sorry @LucaCappelletti94, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 2 days and 22 hours by commenting @sourcery-ai review. Upgrade to get a review now.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository: LucaCappelletti94/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 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 |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThe translator now explicitly handles sqlparser’s Flow diagram for CREATE FOREIGN TABLE translationflowchart LR
A[CREATE FOREIGN TABLE] --> B[Statement translator]
B --> C[drop_with_warning]
C --> D[Emit no SQLite statement]
C --> E[REASON_FOREIGN_DATA]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #106 +/- ##
=======================================
Coverage 92.79% 92.79%
=======================================
Files 66 66
Lines 28263 28264 +1
=======================================
+ Hits 26226 26227 +1
Misses 2037 2037 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|



sqlparser main added
Statement::CreateForeignTablein apache/datafusion-sqlparser-rs#2515. The statement translator matchesStatementwith no wildcard arm so that every new variant gets classified on purpose, and pg2sqlite stopped compiling against sqlparser main as a result.A foreign table reads its rows through a server and a wrapper that SQLite has no counterpart for, so
CREATE FOREIGN TABLEjoinsCREATE SERVERand the connector and secret statements. It emits nothing and reports a lossy drop warning with the shared foreign data reason.Summary by Sourcery
Classify unsupported
CREATE FOREIGN TABLEstatements as lossy drops with foreign-data warnings.Bug Fixes:
CREATE FOREIGN TABLEstatements so they no longer prevent compilation against newer sqlparser versions.Enhancements:
CREATE FOREIGN TABLEstatements with the standard lossy foreign-data warning.Tests:
CREATE FOREIGN TABLEis classified as a warned, lossy drop.