use DuckDB’s auto delimiter by default #325
Merged
Conversation
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
Fil
approved these changes
Nov 21, 2022
There was a problem hiding this comment.
This will be particularly useful for French users of Excel, since by default Excel localizes csv with a semicolon delimiter (because it also uses commas instead of dots for decimal numbers…). Which explains why we have awful lots of semicolons-separated-values files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Rather than hard-coding CSV = comma and TSV = tab (despite the name), use DuckDB’s magical automatic delimiter inference by default. You can still specify a delimiter explicitly if you use the delimiter option.
Ref. https://observablehq.com/d/f11bdd2a9af411c5