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
Wrong backup order for character sets and collations [CORE1064] #1485
Comments
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 [ 10041 ] |
Modified by: @asfernandesFix Version: 2.0.1 [ 10090 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarVersion: 2.1 Initial [ 10160 ] Version: 2.0.0 [ 10091 ] => Version: 2.0.1 [ 10090 ] => Version: 2.1.0 [ 10041 ] => |
Commented by: @pcisar Reopened to update ticket information. |
Modified by: @pcisarWorkflow: jira [ 11424 ] => Firebird [ 15160 ] |
Modified by: @pavel-zotovQA Status: No test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @asfernandes
Character sets and collations is being backed-up after tables, hence they are restored after tables.
This obviously don't work when restoring with -ONE_AT_A_TIME, when a table uses non-system charsets or collations.
Commits: 1955e81 2216487
The text was updated successfully, but these errors were encountered: