Closed chapmanjacobd closed 1 year ago
The scientific notation bit is actually partly a fault of JSON as a standard. JSON - according to the spec - doesn't support integers, everything is a float, and for very big floats they're printed in scientific notation.
The nil bit I agree, thanks for the report!
Both of these have now been fixed in https://github.com/cube2222/octosql/commit/2e6b0cdb2fc53660ebebdc243bd397df348b0351 and released in 0.11.1.
Thanks for the report!
I don't think it should be printing in scientific notation... ? I just want an
int
Also not sure why are there also... is nil "null" in go? While there is not standard for CSV, the convention is no char output:
1,,3
There is probably a good CSV library in
go
which can ensure proper quoting, etc ??