-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
cockroach dump INSERTs do not include collate clauses #48278
Comments
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
Thanks for the report. cc #28948 |
We'll investigate. |
cc @dt for triage |
@rohany should |
It should, and the corresponding format function on |
Documented in cockroachdb/docs#7311. |
48687: cli: fix `cockroach dump` with collated strings r=dt a=rohany Fixes #48278. Release note (bug fix): Fix a bug where `cockroach dump` on a table with collated strings would omit the collation clause for the data insertion statements. Co-authored-by: Rohan Yadav <rohany@alumni.cmu.edu>
Fixes cockroachdb#48278. Release note (bug fix): Fix a bug where `cockroach dump` on a table with collated strings would omit the collation clause for the data insertion statements.
Fixes cockroachdb#48278. Release note (bug fix): Fix a bug where `cockroach dump` on a table with collated strings would omit the collation clause for the data insertion statements.
Describe the problem
If you are using tables with columns that use collation, the SQL generated by
cockroach dump
won't insert without massaging the queries.To Reproduce
cockroachdb dump --insecure db > sql
[2]cat sql | cockroachdb sql --insecure -d db
, see error [3]Expected behavior
I expected the dump sql to include the necessary
collate en_u_ks_level2
clause. I think, anyway -- is there a better way?Additional data / screenshots
[1]
[2]
[3]
Environment:
The text was updated successfully, but these errors were encountered: