Hi all
I have an app with user table having too many columns, because we’re tracking the user activity across a productivity app in different sub-modules, so every time user makes a ‘create’ or ‘update’, we’re creating a log table entry - linked to user table as {1 user : Many log table entries} - and in action we simple fetch the ‘logged in user’ in each sub-module.
There are 20+ such sub-modules, so we end up with many columns for capturing user activity.
My questions are -
- Can we reduce the number of such relationship columns by using a join table like a ‘User Profile’ table, and instead of capturing logged in user we capture the logged in user’s User Profile Entry?
This is a 1:1 relationship between User Table and User Profile Table (1 User table entry : 1 User Profile Table entry), but I don’t know how to implement 1:1 in Adalo correctly, as only options are 1:M and M:1, and generally this ends up having to create a single entry as a list or fetching a full list on screen and filtering then going to detail page to get ‘Current Item’ data on next screen, even when it is a single entry for a related entity. What is the best way to implement such 1:1 join tables? Is this the only way to implement join tables?
- How many relationships is too many? I know its subjective and app dependent and all that, but in experts experience with Adalo, what limit gives good performance? Not just about User table, but any table in general in Adalo, what’s a good limit for number of relationship columns in a single table, before we need to split off and start using ‘join’ tables?
Thanks.