Hi there.
I’m new to backendless and I would like to know if there’s any tech recommendation as to establish table relations in one or other direction, particularly on the impact over performance of querying. I mean having a one-to-many on parent table, or one-to-one on child table. We’re trying to define a global approach for both composition and association relationships.
If you can help me or just put me on the right path it would be greatly appreciated.
Many thanks in advance,
Paulo
Hi @Paulo_Mira,
In terms of technical recommendations for establishing table relationships in Backendless, the performance impact between different relationship types (like one-to-many on a parent table or one-to-one on a child table) remains the same. Under the hood, Backendless handles relationships as many-to-many, so there is no meaningful difference in query performance based on the direction you choose for relationships.
However, as a general rule, following relational database best practices would be the right approach - designing your relationships to reflect the logical structure and behavior of your data.
Best regards,
Stanislaw
Hi Stanislaw.
Thanks very much for your clear explanation.
Very important to know that always has many-to-many to implement relations.
Paulo