and it looks kinda cool. I was going to take it out because I'm not sure what it could break, but I'm thinking about just leaving it there.
I think I just made a coworker's day. I just noticed she has an accent above a letter in her name: é She always just uses a plain e on the computer, but then I remembered this emoji thing. Hey, if someone can have a in their name, then surely they can have an é. I decided to try that in her nickname so it will show up that way on most reports but leave the plain e in the first name field for searching purposes. Hopefully, it won't break anything.
Go into SQL, right-click the Arena Database and select properties. On the General tab, there's a property for "Collation". You should see something like General_CI_AS. That "CI_AS" part determines if it is Case Insensitive (CI) in the search. It also has Accent Sensitive (AS). If that AS were changed to an AI (Accent Insensitive), then the search would match café when you have a WHERE name = 'cafe' query, as well as your coworker's name.
Maybe check with Arena Dev/Support and see if it is supported to update the Collation setting on the database, or maybe just the Name fields in the core_person table.
Interesting. I did some more reading, and it sounds like something best done when setting up the server. Fortunately, I am planning to migrate to a new one soon.
You can also cast the collation on the query itself and not have to touch the database, just don't know how that would affect performance.