No "hierarchical" option in List views for second-level DB?

[cannibalflea]

I offered a possible way of achieving this here:

@cannibalflea

I believe the simplest case would be to first start with the current database relation as the primary parent and if no relation is defined to the same database (i.e. relation is null), then we would go up one level and use that relation as the parent relation (if it exists). And so on up the levels until you get to the first level at which point if no relation exists, it gets captured under a “no parent” bucket.
…
Approach
Start by building each databases’s nested structure first (which is what fibery does for the first level):

Then in step 2, you start from highest level and move up and try to map all the root/level 1 items in the lower level databases:

There was also a discussion further down the same thread on impacts on both 1-many and many-many relations.

I do hope there is a solution to this at some point as it allows for many interesting possibilities.