After reviewing the notes in #1722084: Need clarification on how uniqueness of a machine name is considered in this module, I've verified that adding more than one instance allows you to create duplicate entries. I can't immediately think of a use case in which multiple "unique identifiers" would be useful, but I'm not ruling it out. The field needs to check against itself in addition to checking against already-existing db values.

I'm going to start working on a patch.

Comments

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

Maybe we need an own validator for this but just an idea. What about using unique_field?
http://drupal.org/project/unique_field

danrod’s picture

danrod
Location Ottawa
commented
Assigned: drnikki » Unassigned
Issue summary: View changes
danrod’s picture

danrod
Location Ottawa
commented

I'm closing this issue given that Drupal 7 is no longer supported and for those who still use the D7 version of this project, the unique_field module should be a good option instead.

danrod’s picture

danrod
Location Ottawa
commented
Status: Active » Closed (outdated)

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.