3 ms·
JSON doesn’t handle int64 or explicit date-time data types, which makes it nearly as painful as CSV in practice when used for data integration. Both of those a
by tatersolid 6y ago
JSON doesn’t handle int64 or explicit date-time data types, which makes it nearly as painful as CSV in practice when used for data integration. Both of those are explicit types present in nearly every real-world database schema.
So you end up with many of the same problems as CSV. You basically get an application-specific JSON dialect to interpret.
Header row or not? Is a long series of digits in quotes an int64? What happens when someone puts an ISO-formatted date string into a field that is supposed to be a simple string?