Respect unique constraint for relations field

[raza2022]

Document Created with Wrong Relation Field ID and Duplicate ID

Let's Say You have a relational field named categoryID in users collection to link with Categories collection, and also this field has a check as unique fields option in advanced settings. So when new user created it should have a valid categoryID which already exists,

Now There are three cases and please make sure my case is 2nd and 3rd as first one already asked in previous issues.

1. categoryID not supplied then user created successfully (not my issue as I know there is notrequired fields feature currently in strapi and it's already asked)

2. wrong categoryID supplied and user still created (that's my case), means you can pass any valid 24 digit mongodb ID from any collection (not from categories) and it will be accepted without any error ?

3. use the same ID again and again it will created new user despite unique fields is checked in advanced settings in relational field??

Steps to reproduce the behavior

1. Go to 'Admin Panel Content Builder'
2. Add new Content Type Categories
3. Go to user collections and add relational field name categoryID to Categories
4. Go in advanced settings tab and check the unique field
5. Create New User from Front End using Strapi SDK or axios with any valid mongodb 24 digit ID and it will created without any error

Expected behavior
It should not create user and throw error that Category with specific ID is not exists or invalid category Id.

System

• Node.js version: 10.16.0
• NPM version: 6.9.0
• Strapi version: 3.0.0-next.11
• Database: MongoDB 3.0.14 Community
• Operating system: Linux Ubuntu 14.04

[derrickmehaffy]

@raza2022 while I know the issue exists on beta please note that the next branch shouldn't be used for testing or any sort of production/development use: Strapi version: 3.0.0-next.11 generally those builds are incomplete, broken, or missing code entirely. Just a reminder 😉

As to the issue you stated, I agree. There needs to be a validation that the relation being referenced actually exists.

[petersg83]

@derrickmehaffy Is it something to close? I'm not sure to properly understand the issue

[sobhardwaj]

this issue in v3, is it still open in new release ??

[derrickmehaffy]

@derrickmehaffy Is it something to close? I'm not sure to properly understand the issue

AFAIK it still does exist in v4 @petersg83 as you can't mark relations as unique (or required but that's more of a feature request)

[petersg83]

What does it mean to have a relation marked as unique?