Performance: Glide Table with Row Owner vs Big Table

Theoretically I think that’s exactly how it will work, since Glide will “scan” the database and apply row owners/roles to that, before letting the user download only what belongs to their account.

In your admin case, if all rows can be seen, then all rows will be downloaded, and I think it will cause performance issues, especially if it goes over 25k.

Naturally, Big Table is the answer, but as you noted, it can come with lack of functionalities compared to the normal table.