John Kerl
John Kerl
@osevill the 6.11.0 release (https://github.com/johnkerl/miller/releases/tag/v6.11.0) contains PR #1479 which addresses issue #1418. Before this, Miller was in some cases producing non-compliant CSV output: ``` $ cat i.j [ { "a":...
@osevill the best option would be to restore the behavior of #1479, default off, only behind a new opt-in flag -- I can do this, no problem.
@tooptoop4 how many columns does the 5GB CSV have? (Also, if possible, can you link to the CSV file itself? No worries if not, but it'd be helpful). The reason...
Thanks @tooptoop4 and @aborruso Also I would note, `xsv` is well-known for speed; there is no assertion that Miller will outperform it for speed ...
Indeed @aborruso I should have mentioned -- the example is quite sufficient -- thank you! :)
Perhaps #379 and this would have the same fix ...
> I get your point that RFC4180 formally applies to CSV files and not necessarily TSV files. But from my experience the two are essentially treated the same except that...
Thanks @SpikyClip !! And thanks for reminding me of the name "IANA" for the (pseudo-)spec which I ended up following on #923. Let's leave this issue open as a doc...
@aborruso I think this question is well-posed @karudonaldson how about: `cat 1546.csv` ``` one,two,three,four,five pan,pan,1,&,10 wye,wye,1,&,20 eks,wye,1,'',10 zee,pan,1,(test),60 ``` `cat 1546.mlr` ``` for (k in ["four"]) { v = $[k];...
I believe this is resolved -- @karudonaldson if I'm mistaken please let me know and we can re-open. Thank you!