How do I switch off these sub-tables features in the database manager ?
When designing queries now, I have to go digging around to find tables that are embedded in others when I really don't want to. And I certainly don't want to ever risk Wappler managing my database relationships on some presumptive field-naming basis -- particularly with millions of records.
Also on the query builder tables are displayed as a list so there isn’t much to dig around …
Furthermore sub tables and reference tables are displayed on the top when picking tables to join so they are actually much easier to find instead of cycling the whole list.
I agree it would’ve been helpful to get a sense of the actual representation of tables in the database server, like it was when experimental mode was on and off
Not a big deal, just something I was expecting at the time
Bump just wondering if there is anyway of disabling sub tables yet? I find them really difficult to follow and just cause confusion. I find myself just undoing the change if a subtable is made and then coming up with some random name for the tbl to prevent it from being a subtable.
I end up with a migration file like this but then the table name is to_depot. After this once I try make changes to this table I get all sorts of errors. Is this table still called users_to_depots or will it now be called to_depot?