If we are supporting this kind of relationships, i think one important option to validate is whether the relationship is
one to one (person - id)
one to many (team members - project)
many to many (c...
If we are supporting this kind of relationships, i think one important option to validate is whether the relationship is
one to one (person - id)
one to many (team members - project)
many to many (classes - students)
I don’t know if SQL-style relationships are necessary, although when modeling certain domains, being able to restrict how many instances of a type of something can be related to another type of something could be essential to ensure correctness of data.
What you’re after is the ability to constrain a relationship’s cardinality.
I believe I stumbled upon some unpolished area of Tana where it’s possible to set cardinality of any given field. I think it might have been an abandoned feature?
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
I don’t know if SQL-style relationships are necessary, although when modeling certain domains, being able to restrict how many instances of a type of something can be related to another type of something could be essential to ensure correctness of data.
What you’re after is the ability to constrain a relationship’s cardinality.
I believe I stumbled upon some unpolished area of Tana where it’s possible to set cardinality of any given field. I think it might have been an abandoned feature?