Open CSV/Parquet/JSON files directly with DuckDB#213
Merged
Conversation
Pointing a DuckDB connection at a data file (e.g. /tmp/sales.csv) now loads it into a real table inside a per-process sidecar .duckdb so the user can run full CRUD against it. Restarting sqlit re-loads from the source file; writing back is explicit via COPY <table> TO '<path>'. Refs #146.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Point a DuckDB connection at a CSV/Parquet/JSON file and sqlit loads it into a real table you can CRUD against. Write back with
COPY <table> TO '<path>'.Refs #146.