I don't like subtables being nested in tables in the database manager

I opened an older project that already uses subtables, and found myself wondering about missing tables. It’s no longer very intuitive to use Wappler’s database manager to get a general overview of the database when you don’t have a previous sense of the database structure. People might revert to external database viewing tools or start using one when they didn’t before…

I wonder why the Wappler team took out the switch they had that allowed to toggle between the old view and the new “nested subtable” view :frowning:

The feature request is for bringing back that switch

My thinking is that the nested sub-tables is good for databases which are created from the start with this in mind but they do seem to cause confusion and uncertainty when using existing databases which happen to have table names that might cause them to nest so having a switch sounds like the ideal solution so it has my vote.