Replies: 1 comment 3 replies
-
Hi @ghnp5, I was not able to reproduce your issue. This is my test case:
Then I run:
without errors. Please, provide a test case so I can help you. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey
My application (PHP) runs on every connection:
SET NAMES utf8mb4 COLLATE utf8mb4_unicode_ci
(except on earlier years, but it's like this for many years already)
--
When running
myloader
, I'm getting this issue:while it's trying to apply a
CREATE TABLE
that has aVIRTUAL GENERATED
field that containsregexp_replace
.--
If I run the
CREATE TABLE
manually, it runs fine.However, I've just realized that the problem is that
mydumper
puts this at the top:/*!40101 SET NAMES binary*/;
--
I understand I can change this by including the parameter
--set-names
in the command.However:
--
I'd like to understand why is
binary
preferred and it's so discouraged to change the--set-names
.What can go wrong if I set to
utf8mb4
?Is it possible to give me an example, please?
Is it just a problem if I have
blob
orbinary
fields?EDIT -- Another question is... can I simply replace the schema files so that those have
SET NAMES utf8mb4 COLLATE utf8mb4_unicode_ci
while the data ones haveSET NAMES binary
?Thank you very much!
Beta Was this translation helpful? Give feedback.
All reactions