[Tickets #9760] Re: QUERY FAILED: Duplicate entry 'xxx' for key 'rampage_users_user_name' INSERT INTO `rampage_users` (user_name) VALUES ('xxx')

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/9760
------------------------------------------------------------------------------
  Ticket             | 9760
  Updated By         | arjen+horde at de-korte.org
  Summary            | QUERY FAILED: Duplicate entry 'xxx' for key
                     | 'rampage_users_user_name' INSERT INTO `rampage_users`
                     | (user_name) VALUES ('xxx')
  Queue              | Kronolith
  Version            | 3.0-RC2
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2014-11-03 12:26) wrote:

> This is caused as the usernames are checked literally instead of  
> case-insensitive.

Which is correct as many backends are case sensitive. If yours is not  
and you want to correct this, Horde provides a preauthenticate hook  
(see horde/config/hooks.php.dist) to change the case to whatever you  
prefer. An example for precisely this use case is provided.

> Ive just had this problem where in the past someone had logged in as  
> 'DAVID' and also as 'david', once I updated the column  
> event_creator_id in the kronolith_events table so it was all the  
> same the upgrade worked fine after. I also had same problem with  
> turba.

This has been discussed many times before already.