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
I don't think row_number() without any ordering parameter has a consistent interpretation in SQL/relational databases in general, and since the dplyr::row_number() is based on SQL2003, it would make sense that it returns an error.
I assume the native row_number() just returns the "original" ordering, like mutate(iris, id = 1:NROW(iris)), but if anything, it seems like this native version should in fact return an error if dplyr is based on a SQL style interface.
If I use row_number() works well, but if I call dplyr::row_number() returns an error
The text was updated successfully, but these errors were encountered: