Slow Database Partial Fix

Hi all,

Just a quick tip for something I’ve only just noticed, which is that the bubble db UI is fully loading every single entry for every single deleted field on any datatype you are viewing. Only just thought to inspect it for the first time in 3+ years, and immediately saw that one of my datatypes was loading multiple megabytes of data from a dead field.

Quickest way to resolve this was to use the app optimisation tool, unselect all (for safety and speed!), then search for the field in question, running the optimiser on that field only. Was an instant fix in my case, for errors I created before I knew how to use the platform properly.

Thought I’d share since it’s saved me a lot of headache, hope it’s helpful.

2 Likes

I would actually add a couple steps. Below is the procedure I follow to remove a no-longer-needed field from the DB:

  1. Remove all references to the field (use the editor search tool).
  2. Delete the field data.
  3. Delete the field itself.
  4. Optimize the app to purge the deleted field from the app.

That’s the way I’ve always done it because it “made sense”, but you can check this recent thread for some insights and rationale.

-Steve

4 Likes

Yeah, I would add one more step just to be safe. Between steps 1 and 2, go into your privacy rules and make sure there’s only a single rule with everything unchecked.

2 Likes