[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127372#comment-17127372
 ] 

ASF subversion and git services commented on OPENMEETINGS-2295:
---------------------------------------------------------------

Commit 542cbbef12670a0fbed7dbbf160012aa0581426f in openmeetings's branch 
refs/heads/master from Maxim Solodovnik
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=542cbbe ]

[OPENMEETINGS-2295] restore will fail if email/login exists


> Multiple Users with same Username and Email
> -------------------------------------------
>
>                 Key: OPENMEETINGS-2295
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2295
>             Project: Openmeetings
>          Issue Type: Bug
>    Affects Versions: 5.0.0-M3
>            Reporter: Kamhamea K.
>            Assignee: Maxim Solodovnik
>            Priority: Major
>         Attachments: multiple_users_active.jpg, multiple_users_deleted.jpg
>
>
> When a user is deleted the same user (identified by username and email) can 
> be created again (see figure 1). This is not so much of a problem, rather 
> normal behavior. However all the doublets can be restore, so the database 
> ends up with multiple users sharing email and username (see figure 2)
> The best solution to this problem would be a unique key in the Mysql-Database.
> [https://stackoverflow.com/questions/635937/how-do-i-specify-unique-constraint-for-multiple-columns-in-mysql]
> The disadvantage is that no user can use the same username and email again 
> even if the user is already deleted. Solutions for uniqueness of only active 
> users are discussed here. 
> [https://stackoverflow.com/questions/46965617/mysql-unique-constraint-of-two-columns-only-if-second-column-is-a-specific-value]
> I suppose the solution of two different tables for active and deleted users 
> is more streamline with the current project.
> Finally, as other databases than MySQL are supported the solution for these 
> databases has to be considered too.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to