+1. read_xxx() should not stop if there are no problems with the table format or type specification for existing columns. With the current behaviour it's hard to read the files with the variable sets of columns, because one doesn't know in advance what columns would be available.
If there's a typo in col_types specification, just a warning should be enough. If the user wants to enforce the existence of the columns, it's also easy to do from the user code.
I would like to specify the column types using arguments
col_typeswhen I read the csv files. However, the column number could be different in my multiple csv files (Some files include extra column).
When I specify extra column types and get an error messages:
It will be better to let us to specify extra columns for flexibility (or give a warning message).
The text was updated successfully, but these errors were encountered: