When might an embedded event detail be reasonable in a wedding database?
Embedding can suit small, bounded information that is usually read with its parent. Consider independent updates, record growth, and duplication before embedding data that has its own lifecycle.
Explore This Question
Search for additional explanations using these tools:
More FAQs in How should relationships between users, weddings, events, guests, and tasks be modeled?
No. The field records ownership, but server logic must still verify the caller's membership and permissions. It must also validate that referenced records share the required scope.
Define the policy explicitly, such as clearing the assignee while preserving the task. Apply the change consistently and prevent the removed collaborator from retaining access through old references.
Still have questions?
Browse all our FAQs or reach out to our support team