You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #10 makes explicit a behaviour that was previously implicit.
Each of the queries modified in that PR should be evaluated for correctness and modified accordingly. As the functionality we've observed seems correct, it's likely that the queries are working correctly, however we should attempt to eliminate usage of ANY_VALUE by correct usage of GROUP BY, aggregate functions such as SUM, or introduction of explicit one-to-one relationships between the variables in the SELECT clause to prevent or minimise hard-to-debug issues in future.
The text was updated successfully, but these errors were encountered:
No, not yet, I'm not aware that anyone has actually done a decent analysis of the usage of ANY_VALUE in the db queries. I somewhat expect that all usages thereof should disappear, but I'm a bit hesitant to declare as much.
PR #10 makes explicit a behaviour that was previously implicit.
Each of the queries modified in that PR should be evaluated for correctness and modified accordingly. As the functionality we've observed seems correct, it's likely that the queries are working correctly, however we should attempt to eliminate usage of
ANY_VALUE
by correct usage ofGROUP BY
, aggregate functions such asSUM
, or introduction of explicit one-to-one relationships between the variables in theSELECT
clause to prevent or minimise hard-to-debug issues in future.The text was updated successfully, but these errors were encountered: