Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Matching the extra columns specified in col_types #145

byzheng opened this issue Apr 21, 2015 · 1 comment · Fixed by #159

Matching the extra columns specified in col_types #145

byzheng opened this issue Apr 21, 2015 · 1 comment · Fixed by #159


Copy link

byzheng commented Apr 21, 2015

I would like to specify the column types using arguments col_types when 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:

Error: The following named parsers don't match the column names: sow_date1

It will be better to let us to specify extra columns for flexibility (or give a warning message).

Copy link

alyst commented May 2, 2015

+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.

alyst added a commit to alyst/readr that referenced this issue May 4, 2015
@lock lock bot locked and limited conversation to collaborators Sep 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
None yet

Successfully merging a pull request may close this issue.

2 participants