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
Since we convert the i argument of joins to data.tables, even scenarios of vectors/lists are handled. This should drastically reduce the occurrence of encoding warnings.
The text was updated successfully, but these errors were encountered:
It would be good to improve the situation with respect to merging on columns with marked encodings. The current warning message is leading to nonsense like http://stackoverflow.com/q/33482308/189946
It would be good to improve the situation with respect to merging on columns with marked encodings. The current warning message is leading to nonsense like http://stackoverflow.com/q/33482308/189946
—
Reply to this email directly or view it on GitHub.
One way to provide better Encoding support is to provide an argument while creating/converting a data.table. That is,
Since we convert the
i
argument of joins to data.tables, even scenarios of vectors/lists are handled. This should drastically reduce the occurrence of encoding warnings.The text was updated successfully, but these errors were encountered: