The great post Dataverse is not a database sets forth how Dataverse is distinguished from an RDBMS, such as SQL Server. The follow-on comment addresses Dataverse's limitations on joins traversing multiple tables.
Since this is a frequent business requirement in complex applications, is there a current recommended best practice for handling it with Dataverse, or if one has this business requirements, is that sufficient reason to conclude that Dataverse is not well suited for the requirement ?
Here is an example scenario:
Hypothetical tables
- Friends (Ann, Bob, Carl, ...)
- Ingredients (Rum, Soda Water, Lemon, Bourbon, Vodka, Champagne, ...)
- Cocktails (Pina Colada, Negroni, French 75, ...)
- Cocktail Ingredients (Pina Colada X Rum, French 75 X Champagne, ...)
- Friends Favorite Cocktails (Ann X Pina Colada, Ann X French 75, Bob X Negroni, ...)
Use case
"Query a list of ingredients needed to make any of Ann's favorite drinks"
This scenario presents all the time in our business requirements.
(Thanks to @ChrisPiasecki for helping me get started with this yesterday.)
