If I am referencing field in a datatype say User->thing
thing is another datatype.
The user create a few database entries that contain User-> thing.
for example:
Thing A =
{ Thing: User. Thing}
Is Bubble looking up user.thing every time and therefore incurring WF or user.thing is already loaded into memory when the page load considering User would have to be loaded at page load?
Is it better to have a custom state = user.thing on page load or it doesn’t really matter?
If user has a field that is another object, then this another object is loaded as well.
Amongst other costs, Bubble bills based on how much data is being loaded from the DB. So yes the heavier your User object is the costier it gets to operate the most basic operations.
Note: we are talking about fractions of fractions of WU, so that might not be a big deal. Maybe it is, depending on your application and how many other optimisations you’ve done.
The unique ID of the other object is loaded, unless somewhere on the page you are referencing a field form that object, only then is the entire set of data from the other object loaded.
It will because it is not already loaded until you ask for data from it, then it is loaded. Also, I believe that if that related field on user data type is a list of things, and you request the data from the User (list field of related objects) :first item field, then all the data of all the objects in that list will be loaded.