We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm seeing an issue where column names are:
A) converted to lowercase (they are uppercase in the SQL) B) cannot be remapped in ruby code (without hacking around in the enumerator).
Would a PR to add the map: {} syntax to CSV exports be mergeable?
map: {}
The text was updated successfully, but these errors were encountered:
Sorry, I don't follow you. Could you paste a snippet of the desired code that you would like to use?
Sorry, something went wrong.
Lets say you have CSV imports and exports, and want round-tripping to work.
You export with:
Foo.select('bar as Baz').copy_to_string
then import with:
Foo.copy_from filename, :map => {'Baz' => 'bar'}
However, the CSV from copy_to_string has a header row of baz, not Baz.
copy_to_string
baz
Baz
I see your point. It makes sense to have symetrical APIs on exports and imports.
No branches or pull requests
I'm seeing an issue where column names are:
A) converted to lowercase (they are uppercase in the SQL)
B) cannot be remapped in ruby code (without hacking around in the enumerator).
Would a PR to add the
map: {}
syntax to CSV exports be mergeable?The text was updated successfully, but these errors were encountered: