Grouper Users - Open Discussion List

["Waldbieser, Carl" <>]

Chris,

Once I added the charset info to the end of the connection URL, the warning 
went away.

Thanks,
Carl

----- Original Message -----
From: "Chris Hyzer" 
<>
To: "waldbiec" 
<>,
 "Gouper Users List" 
<>
Sent: Thursday, December 3, 2015 8:07:35 AM
Subject: RE: UTF-8 warning when upgrading a testing database

It just checks one table (grouper_ddl).

When I got this to work with mysql, I had to use this connect url (see suffix)

hibernate.connection.url = 
jdbc:mysql://localhost:3306/grouper_v2_2?CharSet=utf8&useUnicode=true&characterEncoding=utf8

If you cant get it working and you want to turn off the check you can in the 
grouper.properties

https://spaces.internet2.edu/display/Grouper/Grouper+internationalization

Thanks,
Chris


-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Waldbieser, Carl
Sent: Wednesday, December 02, 2015 4:02 PM
To: Gouper Users List
Subject: [grouper-users] UTF-8 warning when upgrading a testing database


I was updating a testing database from Grouper v2.2.1 to v2.2.2.  When I ran 
`gsh -registry -check`, I got the warning:

  Error: Cannot properly read UTF string from database: '???????', make sure 
your database has UTF tables and perhaps a hibernate.connection.url in 
grouper.hibernate.properties

I went through the MySQL tables and made sure to change them all to charset 
utf8 with collation utf8_bin (some of the views still show the previous 
collation for some reason).  However, the warning persists.

Is there a particular table it is writing to to make this determination?

Thanks,
Carl Waldbieser
ITS Systems Programmer
Lafayette College