MariaDB - avoid using correlated sub-queries #14630
Merged
Commits on Sep 20, 2024
-
Fixing an issue that was stopping the limit from being applied to MyS…
…QL, it needs to wrap the query the same as all other DBs, however it needs to apply the where statement in a slightly different manner.
Commits on Sep 23, 2024
-
-
Updates to limit the response of JSON_ARRAYAGG in mysql/mariaDB - rat…
…her than using a limited sub-query which is dis-allowed in MySQL/MariaDB due to the nature of the correlated sub-query.
-
-
Commits on Sep 24, 2024
-
-
Merge branch 'fix/mysql-correlated-queries' of github.com:Budibase/bu…
…dibase into fix/mysql-correlated-queries
-
-
Adding a separation for MariaDB and MySQL, mariaDB is the core of the…
… problem, this solves for it by separating them and allowing us to use the special json_arrayagg for mariaDB, but use a correlated sub-query for MySQL.
-
-
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.