When setting a 1:1 relation, in the generated Prisma schema the @unique attribute is not added and not generated.
What you expected to happen
I expect to see in the UI the unique toggle on and in the generated Prisma schema the @unique attribute on the field represents the fk hoder on the relation
After discussion, we want to perform the fix only on the DSG side so it will enforce the uniqueness without the need to do any guards/changes in the client.
What happened?
When setting a 1:1 relation, in the generated Prisma schema the
@unique
attribute is not added and not generated.What you expected to happen
I expect to see in the UI the unique toggle on and in the generated Prisma schema the
@unique
attribute on the field represents the fk hoder on the relationHow to reproduce
Amplication version
1.7.7
Environment
No response
Are you willing to submit PR?
No response