Grouper Users - Open Discussion List

["Wessel, Keith" <>]

Thanks, Gabor.

I was just talking to Erik about this and said we could easily change the 
default collation for the database, but I wasn't sure how to change what 
Amazon created by default. The parameter groups are the answer to that.

This should dot he trick.

Thanks,
Keith


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

 
<>
 On Behalf Of Eszes, Gabor
Sent: Tuesday, May 22, 2018 3:05 PM
To: Coleman, Erik C 
<>;
 

Subject: [grouper-users] Re: Error about MySQL bin collation

This sounds similar to a post from 2016 [1], where the fix was changing the 
collation setting to utf8_bin, which is what the error message tries to 
reference.

In RDS you should be able to change the collation by issuing an alter [2].

[1] https://lists.internet2.edu/sympa/arc/grouper-users/2016-09/msg00020.html

[2] 
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html


________________________________________
From: 

 
<>
 on behalf of Coleman, Erik C 
<>
Sent: Tuesday, May 22, 2018 3:56:46 PM
To: 

Subject: [grouper-users] Error about MySQL bin collation

I have Grouper successfully connecting to an AWS RDS instance, running 
MariaDB. But at startup, I'm getting this error:

[pool-3-thread-1] ERROR GrouperStartup.verifyUtf8andTransactionsHelper(462) - 
- Error: Queries in your database seem to be case insensitive, this can be a 
problem for Grouper, if you are using MySQL you should use a bin collation

My connection string is as follows:

hibernate.connection.url = 
jdbc:mysql://xxxx.us-east-2.rds.amazonaws.com:3306/grouper?CharSet=utf8&useUnicode=true&characterEncoding=utf8

Any suggestions? I didn't have any different options when running a local db 
instance running straight MySQL, so I'm not sure if this is a MariaDB thing?

Thanks!

Erik Coleman
University of Illinois at Urbana-Champaign