You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is unclear to me why you RECOMMEND only using a text qualifier if there is a field delimiter or other awkward character, as opposed to having file structure consistency.
The text was updated successfully, but these errors were encountered:
It produces simpler CSV data for fields where quoting is not needed, which in my opinion makes it easer to work with the data overall compared to if every field is always quoted.
It hopefully encourages CSV library developers to properly consider the possibility of files and records having a mixture of quoted and unquoted fields. Over the years I've seen quite a few libraries that always quotes every field on output, and fail to parse CSV data if all fields are not quoted, or if there's a mixture of quoted and unquoted fields.
I hope that answers your question, if not, I'm happy to discus further.
It is unclear to me why you RECOMMEND only using a text qualifier if there is a field delimiter or other awkward character, as opposed to having file structure consistency.
The text was updated successfully, but these errors were encountered: