4 ms·
Agreed - the user_ids and team_ids example was a personal flag for me based on my experience with nosql. In that type of scenario I recommend: - memberships co
by dfischer 10y ago
Agreed - the user_ids and team_ids example was a personal flag for me based on my experience with nosql.
In that type of scenario I recommend: - memberships collection and model that under a separate domain.
Separation of concerns also seem like they weren't properly handled so it led to cruft.
- subpixel 10y agoThe Firebase docs don't recommend join tables - their relationship examples are like this (apologies for formatting): "groups": { "techpioneers": { "name": "Historical Tech Pioneers", "members": { "alovelace": true, "ghopper": true, "eclarke": true } } The docs also contain examples of how to manage removing both sides of these sorts of relationships using promises. Still - I think using Firebase for your 'full stack' isn't a wise plan for the long term if your app is pushing the limits of what Firebase is good at.