Escape backslashes in PDODBMultiIngestor for MySQL LOAD DATA INFILE #52
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.
Description
Escape backslashes in data fields.
Motivation and Context
Backslashes must be escaped in data fields (see https://dev.mysql.com/doc/refman/5.5/en/load-data.html). Depending on what character directly follows the backslash a variety of issues arise. If a field contains only a backslash it escapes the enclosing character corrupting all data that follows.
Tests performed
Shredded and ingested data containing a backslash. Confirmed that the correct data was ingested.
Types of changes
Checklist: