Wow, thanks. Very detailed and mind opening.
Could you please explain which type of table are you referring to here? Is it a general table for “project types”?
Text strings, not crazy long.
So we come back to the same conclusion: Glide is a small database platform.
If my original “vision”, every single aspect/element is a table on its own. This is the most organized, most easy to manage and even most easy to back up. For example: A client table, linked to a projects table, linked to an activities table, linked to a messages table and so on. It’s also somewhat more futureproof. Each time we wish to add an aspect/dimension, we simply add a table and a relation to it. I am still having trouble to believe that Glide is always assuming the apps are meant to run 100% on mobile device. This is the explanation I got for the row limit. However, this explanation doesn’t explain the limits on the Pages platform, meant for larger screens, with heavier computing power. All discussed here with @david
Yeah. I understand that @Darren_Murphy is working on something like this. Hope he’ll share some more insight soon.