We are still facing the issue in the bug description, so we have the need :)
Is the answer on so everything we have to change?
-----Ursprüngliche Nachricht-----
Von: Hynek Mlnarik [mailto:hmlnarik@redhat.com]
Gesendet: Wednesday, June 7, 2017 12:05 PM
An: Marc Tempelmeier <marc.tempelmeier(a)flane.de>
Cc: keycloak-user(a)lists.jboss.org
Betreff: Re: [keycloak-user] UTF8 encoding prior v2.5
You don't need to change DB if latin1 satisfies your needs. Otherwise, there are few
ways to change encoding in MySQL, see e.g.
https://stackoverflow.com/questions/6115612/how-to-convert-an-entire-mysq...
--Hynek
On Tue, Jun 6, 2017 at 3:44 PM, Marc Tempelmeier <marc.tempelmeier(a)flane.de> wrote:
Hi,
we updated our Keycloak 2.4 to 3.1, there was a bug in 2.4:
https://issues.jboss.org/browse/KEYCLOAK-3439
Our database is still latin 1 though after the update, does anyone know what we should
change that the data gets correctly into mysql?
Best regards
Marc
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
--Hynek