Multiple Uniqueness Constraints per Content Type

Created on 15 December 2008, about 16 years ago
Updated 18 April 2024, 8 months ago

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.

✨ Feature request
Status

Closed: outdated

Version

1.0

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States GuyPaddock

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡¦Ukraine AstonVictor

    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

Production build 0.71.5 2024