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
Currently, unark() takes the table name as the basename of the .csv file. This name may not be SQL-compliant, leading to quoting, which is a bit of a mess.
unark() should strip out non-compliant characters by default.
unark() should also be more flexible, allowing the user to specify the corresponding table names manually, rather than enforcing they correspond with the incoming csv names.
The text was updated successfully, but these errors were encountered:
- `unark()` will strip out non-compliant characters by default.
- `unark()` is also be more flexible, allowing the user to specify the corresponding table names manually, rather than enforcing they correspond with the incoming csv names. [#18](#18)
- Technical tweak: readLines call inside `unark()` method will use encoding directly from `getOption("encoding")`, e.g. allowing encoding to be set to UTF-8.
This can resolve parsing errors when using the readr parser on certain files. See `FAO.R` example in `examples` for an illustration.
cc @noamross
Currently,
unark()
takes the table name as the basename of the.csv
file. This name may not be SQL-compliant, leading to quoting, which is a bit of a mess.unark()
should strip out non-compliant characters by default.unark()
should also be more flexible, allowing the user to specify the corresponding table names manually, rather than enforcing they correspond with the incoming csv names.The text was updated successfully, but these errors were encountered: