I have been reading up on Bubble Database design, specifically how to handle data linking.
The Bubble Manual is a good resource: https://manual.bubble.io/working-with-data/connecting-types-with-each-other
But I also came across this awesome resource from AirDev (@vlad / @stephanie): https://docs.airdev.co/canvas/using-bubble/bubble-best-practices/database
In a nutshell, they suggest you start off with a one-way link by adding a field to the “subordinate” data type. But if the relationship will be used frequently AND the list will remain relatively small if implemented you can add another field on the “dominate” data type to create a two-way link.
I like this advice because I like simple rules of thumb.
But I’m wondering why they suggest starting with a one-way link on the “subordinate” data type, instead of starting with a one-way link on the “dominate” data type. What is the reason for this?
I find myself having to create a lot of “Do a search for” connections in the editor when the one-way link points from the “subordinate” to the “dominate” data type. Which if I understand correctly, will make the query slower.
I can reverse the direction from “dominate” to “subordinate”, but I’m early on in my database design and I want to make it as using best practice.
So what is the reason why they advise you point from the “subordinate” datatype to the “dominate” datatype?