While looking at an issue with <@1231860789355347971> we saw that the console was displaying ALL databases as TablesDB even if the real type in the API is legacy.
Screenshot 1 : shows all 5 databases as TablesDB in the UI Screenshot 2 : shows GET /tablesdb returning all 5, tho showing different types Screenshot 3 : shows GET /databases returning the 3 legacy databases only
I think the UI should show the legacy as Databases with TablesDB compatiblity instead of directly showing TablesDB for them
Legacy work exactly as TablesDB, legacy is only used internally for our own maintenance, they are first class TablesDBs.
Hmm thanks for the mentioning me and yeah due to this my extension was having the problem of db displaying
<@564158268319203348> but it will be nice for labeling them as when doing so the TablesDB was not displaying but the legacy ones are only displaying
And thanks to <@493852865907916800> we were able to identify the issue and solved it
Recommended threads
- How to update from 1.8.1 to 1.9.6
Due to the number of issues reported in version 1.9.5, I am hesitant to proceed with the update. Could anyone advise if version 1.9.6 is stable and resolves tho...
- [1.9.5] Google OAuth do not work anymore
After migrating to 1.8.1 to 1.9.0 then 1.9.5 and login through Google I get on Flutter app "Missing redirect URL" "Your OAuth login flow is missing a proper re...
- Fatal error: Allowed memory size of 5368...
Hi how solved it worker-messaging infinite reload ` Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 28672 bytes) in /usr/src/co...