Con la versione 10.6 il set di caratteri utf8 è un alias di utf8mb3 e non più utf8mb4.
Io ho risolto inserendo nel file my.ini:
old-mode=
character-set-server=utf8mb4
poi nelle mie applicazioni in C# dopo la connessione eseguo la query:
"SET character_set_results=utf8mb4"
Così ho risolto, ma chiedo:
1. perchè non funziona la direttiva che posso inserire nel file my.ini
init-connect='SET character_set_results=utf8mb4;'
che se ho capito bene dovrebbe essere eseguita ad ogni connessione, ma così non è.
2. è possibile che tutto questo possa essere deciso in fase di setup, magari con un flag del tipo:
"forza l'uso di utf8mb4 come character set di default"
Spero di essermi spiegato bene.
Grazie
With version 10.6 the utf8 character set is an alias of utf8mb3 and no longer utf8mb4.
I solved it by inserting in the my.ini file:
old-mode =
character-set-server = utf8mb4
then in my applications in C # after the connection I execute the query:
"SET character_set_results = utf8mb4"
So I solved, but I ask:
1. because the directive that I can insert in the my.ini file doesn't work
init-connect = 'SET character_set_results = utf8mb4;'
that if I understand correctly it should be performed on every connection, but it is not.
2. it is possible that all this can be decided during the setup phase, perhaps with a flag like:
"force use of utf8mb4 as default character set"
I hope I explained myself.
Thanks
Con la versione 10.6 il set di caratteri utf8 è un alias di utf8mb3 e non più utf8mb4.
Io ho risolto inserendo nel file my.ini:
old-mode=
character-set-server=utf8mb4
poi nelle mie applicazioni in C# dopo la connessione eseguo la query:
"SET character_set_results=utf8mb4"
Così ho risolto, ma chiedo:
1. perchè non funziona la direttiva che posso inserire nel file my.ini
init-connect='SET character_set_results=utf8mb4;'
che se ho capito bene dovrebbe essere eseguita ad ogni connessione, ma così non è.
2. è possibile che tutto questo possa essere deciso in fase di setup, magari con un flag del tipo:
"forza l'uso di utf8mb4 come character set di default"
Spero di essermi spiegato bene.
Grazie
With version 10.6 the utf8 character set is an alias of utf8mb3 and no longer utf8mb4.
I solved it by inserting in the my.ini file:
old-mode =
character-set-server = utf8mb4
then in my applications in C # after the connection I execute the query:
"SET character_set_results = utf8mb4"
So I solved, but I ask:
1. because the directive that I can insert in the my.ini file doesn't work
init-connect = 'SET character_set_results = utf8mb4;'
that if I understand correctly it should be performed on every connection, but it is not.
2. it is possible that all this can be decided during the setup phase, perhaps with a flag like:
"force use of utf8mb4 as default character set"
I hope I explained myself.
Thanks
Con la versione 10.6 il set di caratteri utf8 è un alias di utf8mb3 e non più utf8mb4.
Io ho risolto inserendo nel file my.ini:
old-mode=
character-set-server=utf8mb4
poi nelle mie applicazioni in C# dopo la connessione eseguo la query:
"SET character_set_results=utf8mb4"
Così ho risolto, ma chiedo:
1. perchè non funziona la direttiva che posso inserire nel file my.ini
init-connect='SET character_set_results=utf8mb4;'
che se ho capito bene dovrebbe essere eseguita ad ogni connessione, ma così non è.
2. è possibile che tutto questo possa essere deciso in fase di setup, magari con un flag del tipo:
"forza l'uso di utf8mb4 come character set di default"
Spero di essermi spiegato bene.
Grazie
----
With version 10.6 the utf8 character set is an alias of utf8mb3 and no longer utf8mb4.
I solved it by inserting in the my.ini file:
old-mode =
character-set-server = utf8mb4
then in my applications in C # after the connection I execute the query:
"SET character_set_results = utf8mb4"
So I solved, but I ask:
1. because the directive that I can insert in the my.ini file doesn't work
init-connect = 'SET character_set_results = utf8mb4;'
that if I understand correctly it should be performed on every connection, but it is not.
2. it is possible that all this can be decided during the setup phase, perhaps with a flag like:
"force use of utf8mb4 as default character set"
I hope I explained myself.
Thanks
0. The option in my.cnf doesn't work, because, as far as I understand, C# applications don't read my.cnf. But MDEV-26107 suggests to specify the charset as the connection option ;CharSet=utf8mb4
1. init-connect does not work for users with SUPER privilege. Because if you make an error in the init-connect statement nobody will be able to connect at all. That's why SUPER users ignore init-connect to be able to login even if nobody else can.
2. during the setup of what? for the server use character-set-server and old-mode as you did. For the client use init-connect or .Net connection option.
Sergei Golubchik
added a comment - This is not a bug, better use mailing lists of zulip for asking questions ( https://mariadb.org/contribute/ ).
0. The option in my.cnf doesn't work, because, as far as I understand, C# applications don't read my.cnf. But MDEV-26107 suggests to specify the charset as the connection option ;CharSet=utf8mb4
1. init-connect does not work for users with SUPER privilege. Because if you make an error in the init-connect statement nobody will be able to connect at all. That's why SUPER users ignore init-connect to be able to login even if nobody else can.
2. during the setup of what? for the server use character-set-server and old-mode as you did. For the client use init-connect or .Net connection option.
I'm sorry but the change of character set, interrupting compatibility
with Net Connector, seems to me an invalidating choice.
There are situations for which manually operating the my.ini file is a
problem.
We distribute an workung time mahagement application ( 1300
installations between Italy and Switzerland ) and often the installer
does not have sufficient skills to operate in this sense, which is why a
choice during the setup phase would be useful.
I don't think it would be a big problem for you, while you would relieve
us of a big problem.
Thanks
Danilo
DANILO GIULIANI
added a comment - I'm sorry but the change of character set, interrupting compatibility
with Net Connector, seems to me an invalidating choice.
There are situations for which manually operating the my.ini file is a
problem.
We distribute an workung time mahagement application ( 1300
installations between Italy and Switzerland ) and often the installer
does not have sufficient skills to operate in this sense, which is why a
choice during the setup phase would be useful.
I don't think it would be a big problem for you, while you would relieve
us of a big problem.
Thanks
Danilo
When I talk about modifying the setup I mean the MariaDB setup:
"mariadb-10.6.4-winx64.msi"it would be enough to add this flag, and then
the setup program does what it has to do,See green circle:
Danilo
DANILO GIULIANI
added a comment - When I talk about modifying the setup I mean the MariaDB setup:
"mariadb-10.6.4-winx64.msi"it would be enough to add this flag, and then
the setup program does what it has to do,See green circle:
Danilo
Bug
Major
MDEV-26107 Cannot set character_set variables in my.ini
This is not a bug, better use mailing lists of zulip for asking questions (https://mariadb.org/contribute/).
0. The option in my.cnf doesn't work, because, as far as I understand, C# applications don't read my.cnf. But MDEV-26107 suggests to specify the charset as the connection option ;CharSet=utf8mb4
1. init-connect does not work for users with SUPER privilege. Because if you make an error in the init-connect statement nobody will be able to connect at all. That's why SUPER users ignore init-connect to be able to login even if nobody else can.
2. during the setup of what? for the server use character-set-server and old-mode as you did. For the client use init-connect or .Net connection option.