Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Do you want to make sure a user has no more than one order assigned to them, or do you want to make sure an order is only assigned to one user? The perspective makes a difference. Why can't a user work on more than one order at a time? The business impact might be fulfilling the same order more than once. Commented Apr 13, 2023 at 20:40
  • User cannot have more than one order assigned to him, that is the business requirement Commented Apr 13, 2023 at 22:25
  • 1
    whatever you end up designing will probably be a reinvention of something that relational databases already do (such as unique indexes, as you mentioned, but probably transactions) Commented Apr 14, 2023 at 8:03