Database object size - one big object OR one light object + linked objects

[hauke.rux]

Hey!

Im planning a pretty big database for my next project right now and wondered how to handle big tables, especially when i want to display them in RGs & search through them. My main question is the blue dot here (this is only an example, the columns prob. don’t make sense)

Imagine i break up a big table into 2 smaller ones, a “light” one that contains everything i need to display / search for in a RG, and a second one with all the remaining information - and i then reference an object of the detailed one in the “light table” (as shown), to have quick access.

If i now display 100 of these “light” objects in a RG, it will obviously download the “light” table information which in the example picture would be 100x 5kb, but will it also download all the “product_details” (100x(1mb+5kb)), or will it just download a reference (say an ID) to the object (100x1kb), and then download the detailed information when i access the “product_details” somewhere?

Edit: Also, would it be more performant on the server side, as it has to serve & search through less information, or would there be no relevant difference?

Thanks for ur help!

[hauke.rux]

^push

[josh24]

Hey @hauke.rux

You’re on the right track. Bubble isn’t going to download all of the linked data unless you request it. You’ll only bring in the product details as required when you break out the product details into a separate table.

So this will improve performance on the server + in the browser

---

Josh @ Support Dept
Helping no-code founders get unstuck fast save hours, & ship faster with an expert on-demand

I post daily about no-code and Bubble on Twitter