4 ms·
Can anybody explain why the function is "jsn_extract" instead of "json_extract"? I thought it was a typo at first...
by ImJasonH 11y ago
Can anybody explain why the function is "jsn_extract" instead of "json_extract"? I thought it was a typo at first...
- scient 11y agoBecause some people should not be allowed to name things, ever.
- jakejake 11y agoI thought that was a bit annoying too. And it's also underscore delimited, when there is already a similar function for XML which is ExtractValue()
- haberman 11y agoI was wondering the same thing, especially since there is precedent for the JSON_EXTRACT name in SQL: https://prestodb.io/docs/current/functions/json.html https://prestodb.io/docs/current/functions/json.html https://cloud.google.com/bigquery/query-reference#jsonfunctions https://cloud.google.com/bigquery/query-reference#jsonfuncti...
- morgo 11y agoThere may be some chance that json_* functions become a standard, but have different call parameters. This design allows MySQL to implement both without the backwards compatibility concern.