Added new feature to force empty values to nil #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new parameter column_names_empty_to_null is used to specify columns for which an empty parameter should be forced to nil (so it becomes a null when inserting to the DB).
This was essential for me where I had a CSV formatted log file I needed to push to various DB columns, but some of the CSV parameters could be "", for things like dates or int's resulting in errors during bulk insert.
With this version you just add those columns to column_names_empty_to_null and they are inserted as NULL to the table.
Perhaps a future improvement could be the possibility to have a mapping of input values to output values - for instance other inputs like - or * or "" could all be considered null. This version I kept simple though.