Is it best practice to attach list of things to users?

[mmm]

Hi,

whenever I create a new thing that is managed by a user (e. g. appointments), I wonder if I should also store the new thing in a user attribute or not. My understanding is that there are two options:

Option A) Create appointment - (going forward, related user is identified via the “created by” field on appointment)

• Pro: Fast creation
• Con: Whenever a repeating group shall display all appointments for a user, a Search function needs to be setup

Option B) (1) Create appointment, (2) add thing to "User’s appointments"

• Pro: Easy to handle going forward - no search function needed to show all of the user’s appointments in a repating group
• Con: Longer creation time because user needs to be updated during creation step

My question is: What is the better approach performance-wise? How do you handle these scenarios and why?

• (A) Use “Created By” field to identify owner of thing - do not add dedicated field to user data type
• (B) Collect new thing on user level (e. g. User’s appointments)

Thanks

[cmarchan]

Hello @mmm

Alternative approach to the Bubble’s recent tutorials for list of things

Hello everybody, I’ve taken a look at some tutorials from the following topic: In short, I think that these tutorials contain some crucial mistakes. Regarding How To Build A Pinterest Clone Without Code Configure your database User [image] We’re facing this mistake on many apps. That’s a wrong approach since it negatively affects performance and speed. Let me explain why I do think that this is wrong. The Bubble’s unique id for each thing looks like the next one: 1583401182457x36677842…

RG vs "Search for" (performance questions)

@rpetribu The conventional wisdom after much time learning from knowledgeable folks in this forum (my understanding of it). And through my own experience building apps is to: build light objects minimize list fields (only when less than 100 entries), only use them purposefully relate objects indirectly but both ways when necessary preload searches feed from preloaded searches avoid inflow searches (… hence preloading them) mnimize back and forths between client and server use custom events ex…

[mmm]

@cmarchan - I cannot thank you enough! Just spend an hour reading using your links. There are some true pearls of bubble wisdom in there. I need to redesign my data types completely.