Show HN: ZSV (Zip Separated Values) columnar data format
github.com
Show HN: ZSV (Zip Separated Values) columnar data format
1–10 of 77 posts
Re: Show HN: ZSV (Zip Separated Values) columnar data format
#2Re: Show HN: ZSV (Zip Separated Values) columnar data format
#3Can't store tabs or newlines, odd choice.
Re: Show HN: ZSV (Zip Separated Values) columnar data format
#4Can't store tabs or newlines, odd choice.
Re: Show HN: ZSV (Zip Separated Values) columnar data format
#5Can't store tabs or newlines, odd choice.
Re: Show HN: ZSV (Zip Separated Values) columnar data format
#6Can't store tabs or newlines, odd choice.
yeah, this is a limitation from the TSV format this is based on - there is an extension to the format that supports storing binary blobs - ref: https://github.com/Hafthor/zsvutil?tab=readme-ov-file#nested...
At least you could use something less likely to appear in data as record sepator (like 0x1E)
Otherwise it's an interesting idea!
Re: Show HN: ZSV (Zip Separated Values) columnar data format
#7Can't store tabs or newlines, odd choice.
yeah, this is a limitation from the TSV format this is based on - there is an extension to the format that supports storing binary blobs - ref: https://github.com/Hafthor/zsvutil?tab=readme-ov-file#nested...
Re: Show HN: ZSV (Zip Separated Values) columnar data format
#8Earlier quoted context omitted.
yeah, this is a limitation from the TSV format this is based on - there is an extension to the format that supports storing binary blobs - ref: https://github.com/Hafthor/zsvutil?tab=readme-ov-file#nested...
(Offtopic, but just FYI) it's tenet (principle) not tenant (building resident).
Re: Show HN: ZSV (Zip Separated Values) columnar data format
#9Re: Show HN: ZSV (Zip Separated Values) columnar data format
#10Earlier quoted context omitted.
yeah, this is a limitation from the TSV format this is based on - there is an extension to the format that supports storing binary blobs - ref: https://github.com/Hafthor/zsvutil?tab=readme-ov-file#nested...
Basically it's the same limitations as CSV. At least you could use something less likely to appear in data as record sepator (like 0x1E) Otherwise it's an interesting idea!