# To relate, or not to relate, that's the question

**URL:** <https://community.glideapps.com/t/to-relate-or-not-to-relate-thats-the-question/45661>\
**Category:** Ask for Help\
**Created:** [July 31, 2022, 7:16pm UTC](https://community.glideapps.com/t/to-relate-or-not-to-relate-thats-the-question/45661 "2022-07-31T19:16:34Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Test\_Test](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/test_test/32/30930_2.png) [@Test\_Test](https://community.glideapps.com/u/Test_Test)\
**Post date:** [August 1, 2022, 10:45am UTC](https://community.glideapps.com/t/to-relate-or-not-to-relate-thats-the-question/45661/3 "2022-08-01T10:45:09Z")

</div>

> [@david](#):
>
> Glide only calculates the relations required to show the current screen

Oh, so it’s not computing all the relations with each change in the database?  
Could you perhaps provide an example for when NOT to use relations, but have duplicate data instead? (or any other solution)

This is bringing us back to the discussions about the 25K limit.

> [@Understanding row limits](https://community.glideapps.com/t/understanding-row-limits/42702/7):
>
> Anyone out there? I asking very seriously: should I avoid using Glide for projects that are expected to exceed the 25K rows limit?

---

_[View the full topic](https://community.glideapps.com/t/to-relate-or-not-to-relate-thats-the-question/45661)._
