# Many to Many Relationships - What am I missing

**URL:** https://community.glideapps.com/t/many-to-many-relationships-what-am-i-missing/80950
**Category:** Ask for Help
**Created:** [March 25, 2025, 12:45pm UTC](https://community.glideapps.com/t/many-to-many-relationships-what-am-i-missing/80950 "2025-03-25T12:45:58Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)
#### Post date: [March 25, 2025, 4:06pm UTC](https://community.glideapps.com/t/many-to-many-relationships-what-am-i-missing/80950/4 "2025-03-25T16:06:22Z")

</div>

Many-to-many relation: create a join table.

It’s not a must, but in most cases I do that. It’s easier to understand the database architecture that way and it prepares your app for future feature development.

> [@Many-to-many Relations](https://community.glideapps.com/t/many-to-many-relations/76753/9):
>
> Welcome to Glide. My approach to building changes all the time, but for the past few weeks I have decided to stop overthinking many-to-many relations. If there is one, I create a ThingsA↔︎ThingsB join table where I write row IDs of ThingsA and ThingsB, and that table is my relation. As soon as I create the table I create a single relation to the table of ThingsA and a single relation to the table of ThingsB, and back the other way. I’m discovering aspects about join tables as I go along, and …

---

_[View the full topic](https://community.glideapps.com/t/many-to-many-relationships-what-am-i-missing/80950)._