will help you In Realtime Database, when a node no longer has any children, it is removed from display in the console. What you are seeing is that the only child of SleepSettings is being removed, which means SleepSettings itself is removed from display. In actuality, a node doesn't really exist in Realtime Database. It's just part of a path to get to a value, such as this path:
I think the issue was by ths following , I just solved this problem. I'm leaving the solution here in case it helps anyone else. In my case, I needed to alter the way I added my data to the database. Initially, I was using:
fixed the issue. Will look into that further If you remove item3, the only child of 1234567, you will always implicitly remove 1234567 because it no longer has children. There is no such thing as an "empty node" in Realtime Database. When a node not longer has children, it is effectively gone, and when you query it, it will yield no data.
Should removeFrom* method remove child item from a DB or it should just remove the parent-child relation?