You glanced over the links quickly at 28:48, so it is not clear if there is an option to have (and enforce) one-to-many and many-to-many links. Could you clarify?
Hi @andrisi 👋 As of this writing, you can have 1:1, 1:M, and M:M relationships. You can also have a self-referencing relationship. However, there's no native way to enforce a specific relationship type. In other words, if you have a relationship that is 1:1 and you'd like to keep it as such, but you're working with a collaborator that has the permissions to edit that relationship, the collaborator would theoretically be able to turn that 1:1 into a 1:M relationship.
![Application Builder 101: How to create applications with Baserow [Webinar]](http://i.ytimg.com/vi/WgMn97AoVqI/mqdefault.jpg)
![Application Builder 101: How to create applications with Baserow [Webinar]](/img/tr.png)
![Build a complete Governance, Risk, and Compliance (GRC) solution without coding [Webinar]](/img/n.gif)
You glanced over the links quickly at 28:48, so it is not clear if there is an option to have (and enforce) one-to-many and many-to-many links. Could you clarify?
Hi @andrisi 👋
As of this writing, you can have 1:1, 1:M, and M:M relationships. You can also have a self-referencing relationship. However, there's no native way to enforce a specific relationship type. In other words, if you have a relationship that is 1:1 and you'd like to keep it as such, but you're working with a collaborator that has the permissions to edit that relationship, the collaborator would theoretically be able to turn that 1:1 into a 1:M relationship.
Perez Robert Taylor Ruth Taylor Sarah