I’m re-evaluating my database structure and want to hear best practice for how folks have joined child and grandchild tables. One reason to get this right is that I’m calling grandchild tables from the API and the “Do search for” strings may be overly complex.
My architecture looks like the following:
Which is the better way to structure the child table? Should the child table reference both fields from the grandparent table (left) or simply reference the parent table (right)?
Reference grandparent table:
Reference parent table:
This may have implications for how I set up the API “do search for”, so I’d like to hear advice from the community.
What’s the best architecture that keeps the API calls simple?