Repository navigation
chore(release): v1.8.1 - #82
Merged
Merged
Conversation
Aggregates SurrealDB can parse: count(), count(field), and math::sum/mean/min/max in place of the COUNT(*) and SUM/AVG/MIN/MAX(...) calls the query builder rendered, which SurrealDB rejects at parse time. Patch rather than minor: the change is a fix with no new API surface, and the old output never executed, so no caller can have depended on it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Cuts 1.8.1. One fix since v1.8.0 (#81), plus two dependency bumps to pinned CI actions.
Fixed
count(),sum(),avg(),min(), andmax()onReadQLandAggregationQueryBuilderrenderedCOUNT(*),SUM(f),AVG(f),MIN(f), andMAX(f), all parse errors on SurrealDB, so every query that used one of these methods failed before it ran. They now rendercount(),count(field), andmath::sum/math::mean/math::min/math::max, with the aliases unchanged.Why patch
A fix with no new API surface. The old output never executed, so no caller can have depended on it.