Case sensitivity discrepancy between front/backend uniqueness rules

[melton-jason]

I am closing this for now. The uniqueness rule has been implemented in v7.9.

However, when verifying this behavior, I did stumble across a bug. The frontend uniqueness rule does its search in a case-sensitive manner while the backend searches and verifies in a case-insensitive way.

For example, if there is a specifyuser called spadmin, the frontend will allow creating a user with name sPadmin, but this will thow a backend exception. This behavior is most likely not specific to this rule, so I will open a new issue (hence the reasoning behind closing this one)

• https://github.com/specify/specify7/issues/3920#issuecomment-1741376567

[realVinayak]

@melton-jason uniqueness rules are done in a case-sensitive manner (if done via uniquenessrules.py). Django queries are case-sensitive.

[melton-jason]

Yes you are correct! My apologies for the misunderstanding.

However, the issue still remains, although it is caused by the database and not related to Django.

if there is a specifyuser called spadmin, the frontend will allow creating a user with name sPadmin, but this will thow a backend exception.

The uniqueness rules should be done in a case-insensitive manner.

As far as backend is concerned, this can be solved by using a filter such as iexact

[realVinayak]

Actually, on testing, django filters are case-insensitive!

Correction: MySQL query was case-insensitive is 'utf8mb4_general_ci' which is case insensitive.

[emenslin]

Can recreate in edge (7.9.6)