I have a project in which there is a content type with two user reference fields, and I need two different uniqueness constraints. The first is that the user specified for the first field cannot be specified for the second one. The second is that no other node can have the same combination of user1 and user2 (i.e. if one node has references to "User1" and "User2", no other node may specify "User1" and "User2", but could specify "User2" and "User1" because it's a directed relation).

The current version requires me to choose which of these two constraints is more important.

Comments

giorgio79’s picture

giorgio79 commented

Been just looking for this as well.

Multiple uniqueness request constraint is a good description.

I have these fields:
title
text1
text2
and I would like title to be unique, plus text1 and text2 together :)

thekayra’s picture

thekayra commented

Something similar to this:

Personally I would like to be able to compare a fields value with mulltiple fields. E.g. field1 of node1 cannot be the same as the field1 and field2 of the node2.

From the number of different request, flexibility is the key for this module.

mautumn’s picture

mautumn commented

+1 subscribing

vacilando’s picture

vacilando commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Issue summary: View changes

Bump; this is much needed indeed.

astonvictor’s picture

astonvictor commented
Status: Active » Closed (outdated)

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks