When using HarperDB hash attributes are case insenstive. This can cause confusion for developers.
For example if you have a user table, it might make sense to use user.email as the hash attribute.
This can cause problems as Harper@harperdb.io and email@example.com would be seen as two different records.
We recommend enforcing case on hash within your app to avoid this issue.