Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
It seems strange to me that JSON functions create loose/non-compact json by default. People would choose the compact format for maximum performance, and if you need to make an extra function call (JSON_COMPACT()), it will kill some of the advantage. Furthermore there should be a minor performance gain in not adding spaces in the first place.
JavaScript's JSON.stringify() also makes the compact format by default. For those who prefer "looser" formats, they still have the JSON_LOOSE and JSON_DETAILED functions, so why not make the JSON_COMPACT the default? At least there could be a server option to select the preferred format.