Database Design
Generic question. I cannot figure out how to design the database in the following scenario:
This can be solved by creating a resource with the same value for each user, but I feel like this is a bad practice.
What other options do I have? I am using EF with Postgres, but I do not think that matters.
OtherTableUsersValueThis can be solved by creating a resource with the same value for each user, but I feel like this is a bad practice.
What other options do I have? I am using EF with Postgres, but I do not think that matters.
