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
In the following example, readxl returns TRUE instead of 599, without any warnings nor errors.
This doesn't happen with xlsx, openxlsx or openxlsx2.
I understand this is related to readxl guessing the column type using the first 1000 rows, but it should return at least a warning if not an error if the data it encounters is incompatible with the column type it guessed.
Yes, I agree. I was recently bitten by this problem - took about a day to figure out!
An alternate solution would be return a character vector rather than a logical vector. In this way, the full information can be captured, i.e. "599" which can be converted to numeric), or the calling program is more likely to return an error when doing arithmetic operations on a character column.
In the following example, readxl returns TRUE instead of 599, without any warnings nor errors.
This doesn't happen with xlsx, openxlsx or openxlsx2.
I understand this is related to readxl guessing the column type using the first 1000 rows, but it should return at least a warning if not an error if the data it encounters is incompatible with the column type it guessed.
test.xlsx
The text was updated successfully, but these errors were encountered: