doc: JSON_OBJECTAGG requires MariaDB >= 10.5 #287
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a bug report in the Icinga Community Forum1 regarding an unknown SQL function when using MariaDB 10.3.39. The function in question was JSON_OBJECTAGG, only being used in one place by web2.
MariaDB's documentation states that this function was introduced in version 10.5.03, greater than the currently documented infimum. This fixes our docs.
This function - or PostgreSQL's used counterpart json_object_agg - is available in the required versions for MySQL and PostgreSQL4 5.
Footnotes
https://community.icinga.com/t/current-state-of-icinga-notifications-modules/14666 ↩
https://github.com/Icinga/icinga-notifications-web/blob/ede7734436ddee952f89295932fbc05e0b4af6e7/library/Notifications/Model/Behavior/IdTagAggregator.php#L58-L59 ↩
https://mariadb.com/kb/en/json_objectagg/ ↩
https://dev.mysql.com/doc/refman/5.7/en/aggregate-functions.html#function_json-objectagg ↩
https://www.postgresql.org/docs/9.6/functions-aggregate.html ↩