feature request #7276: Make User.email a unique field. - Edit - Redmine

feature request #7276

Make User.email a unique field.

Added by Andreas Müller over 3 years ago. Updated about 1 year ago.

Status:

Feedback

Priority:

New

Assignee:

Andreas Kohlbecker

Category:

cdm

Target version:

CDM UML 5.26

Start date:

02/19/2018

Due date:

% Done:

50%

Severity:

normal

Description

Make User.email a unique field.

In the context of password recovery it seems also a requirement to make the email address unique in the UserAccount table.
In order to recover a password the user can usually either supply the login or email address.

NOTE: As long as #7275 is not implemented or if it is rejected it is NOT possible to implement by standard

@Column(unique = true)

as NULL values are duplicates otherwise.

Related issues

Associated revisions

Revision b28a9050 (diff)
Added by Andreas Müller about 3 years ago

fix #7276 Make User.emailAddress a unique field

Revision 80cbc741 (diff)
Added by Andreas Müller about 3 years ago

ref #7276 revert "make User.email a unique field"

Revision 612548d6 (diff)
Added by Andreas Müller about 3 years ago

ref #7276 revert "make User.email a unique field"

History

#1 Updated by Andreas Müller over 3 years ago

Copied from feature request #7275: [DISCUSS] Require email address for Users added

#2 Updated by Andreas Müller over 3 years ago

This only makes sense if email is an obligatory field, which currently is not the case and probably also will not be the case in future.

#3 Updated by Andreas Müller about 3 years ago

Status changed from New to Resolved
% Done changed from 0 to 50

#4 Updated by Andreas Müller about 3 years ago

Description updated (diff)
Status changed from Resolved to New

#5 Updated by Andreas Müller about 3 years ago

Status changed from New to Resolved

Applied in changeset cdmlib|b28a90506f2310c1ebf51dcd2b939ef92814c0be.

#6 Updated by Andreas Müller about 3 years ago

Status changed from Resolved to Feedback
Assignee changed from Andreas Müller to Andreas Kohlbecker

For now I suggest to reject this feature request as long as NULL values are allowed (#7275).

We could only try to check programmatically if an email address already exists. Also we could try to write a validation rule NullOrUnique. But these solutions might be new tickets. What do you think?