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
As discussed in #118, the default translations for pmin() and pmax() are LEAST and GREATEST, respectively.
However, for Snowflake (akin to Oracle), LEAST and GREATEST do the following (in contrast to many other backends, discussed with Snowflake here and a community-identified workaround here):
If any of the argument values is NULL, the result is NULL.
fh-mthomson
changed the title
na.rm = TRUE not respected in pmin()/pmax for Snowflake
na.rm = TRUE not respected in pmin/pmax for Snowflake
Jul 8, 2023
As discussed in #118, the default translations for
pmin()
andpmax()
areLEAST
andGREATEST
, respectively.However, for Snowflake (akin to Oracle), LEAST and GREATEST do the following (in contrast to many other backends, discussed with Snowflake here and a community-identified workaround here):
Accordingly:
na.rm = TRUE
topmin()
andpmax()
, it's silently ignored currently (related to dbplyr translation ofpmax
/pmin
throws an error if it receives the na.rm = TRUE argument #479)I'd expect either:
na.rm = TRUE
is supported ORna.rm = TRUE
errors when called on Snowflake (and does not warn whenna.rm = FALSE
)Illustrative Code (masking company Snowflake instance):
The text was updated successfully, but these errors were encountered: