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
release-22.1: sql: various COPY improvements #78417
Conversation
Release note: None
Release note: None
Release note: None
Add `ESCAPE` logic to the `encoding/csv` package, for exposure to SQL at a later stage. It is worth noting I wrote this in the "safest" backportable way possible. Ideally we'd rewrite the read logic to be more "parser"-like to account for the change in QUOTE case, but that's a lot riskier to backport. Release note: None
Release note (sql change): Implemented the `COPY FROM ... ESCAPE ...` syntax.
62df0c5
to
8da094a
Compare
Thanks for opening a backport. Please check the backport criteria before merging:
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
Add a brief release justification to the body of your PR to justify this backport. Some other things to consider:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @blathers-crl[bot], @otan, and @rafiss)
pkg/util/encoding/csv/reader.go, line 132 at r1 (raw file):
Comma rune // Escape, if unset, is the character used to escape certain characters
Nit: missed this yesterday - should this be "if set"?
Release note: None
Backport 5/5 commits from #78303 on behalf of @otan.
/cc @cockroachdb/release
Refs: #41608
See individual commits for details.
Release justification: low risk new feature for tactical support of third party tool