Skip to content
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

Error importing mysqldump with incorrect string value #8580

Open
timsehn opened this issue Nov 21, 2024 · 3 comments
Open

Error importing mysqldump with incorrect string value #8580

timsehn opened this issue Nov 21, 2024 · 3 comments
Assignees
Labels
bug Something isn't working customer issue import no repro Bugs that can't be reproduced easily

Comments

@timsehn
Copy link
Contributor

timsehn commented Nov 21, 2024

Potential customer reports not being able to import a dump that works in MySQL.

Error is:

ERROR 1105 (HY000) at line 2517838: incorrect string value: '[111 114 103 46 115 112 114 105 110 103 102 114 97 109 101 119 111 114 107 46 111 114 109 46 106 112 97 46 74 112 97 83 121 115 116 101 109 69 120 99 101 112 116 105 111 110 58 32 99 111 117 108 100 32 110 111 116 32 101 120 101 99 117 116 101 32 113 117 101 114 121 59 32 110 101 115 116 101 100 32 101 120 99 101 112 116 105 111 110 32 105 115 32 111 114 103 46 104 105 98 101 114 110 97 116 101 46 101 120 99 101 112 116 105 111 110 46 71 101 110 101 114 105 99 74 68 66 67 69 120 99

Looks like a potential string termination issue.

The customer may be able to provide the scrubbed table schema but will not be able to provide the query or the dumpfile so we may have some trouble reproing this.

@timsehn timsehn added bug Something isn't working no repro Bugs that can't be reproduced easily customer issue import labels Nov 21, 2024
@timsehn
Copy link
Contributor Author

timsehn commented Nov 21, 2024

From Max:

this is triggered when the column is a varchar and the value is not utf-8

@timsehn
Copy link
Contributor Author

timsehn commented Nov 21, 2024

From the private schema the customer shared, it seems that the table has a latin1 encoding and individual varchar columns have utf8mb4 encoding. I wonder if Dolt is not overriding column charsets from the table charset.

@Hydrocharged
Copy link
Contributor

This is potentially fixed by dolthub/go-mysql-server#2758

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working customer issue import no repro Bugs that can't be reproduced easily
Projects
None yet
Development

No branches or pull requests

2 participants