'DataGrip connected to the live MariaDB does not display all the tables in the Database Explorer pane, only 15 are visible
I'm using DataGrip v 2021.3.4 of JetBrains. I connect to MariaDB hosted in AWS. The database has 28 tables, though only fifteen (15) are displayed in the Database Explorer.
Interesting thing is, I can see all the tables if I go to "show visualization":

So far this is my only workaround to get to any of the 'hidden' tables, as the visualization window allows me to right-click and select "jump to source", from there I can work on the table or switch to "edit-data" if needed:

This would be an acceptable workaround if the table names and column names were recognized and hopefully auto-populated with the DataGrip interface, but instead, I get the red-underlined table names in my .SQL with errors displayed saying that:
Unable to resolve table 'table name'
Just to clarify, executing my queries actually works and I get the expected result. The problem is that I compose my queries in the blind.
Things I've tried:
- refreshing the list of tables.
- disconnecting and reconnecting to the live database.
- searching for a possible solution in here, on the StackOverflow website.
Anything else you would recommend me to try?
Thank you,
Update #1 [May 1, 2022]: Upgraded DataGrip to 2022.1.2, removed some tables, down to 21 total, still limited to 15. Some more details, in case this becomes a question: MacOS v11.2.3 (BigSur), 16-core Intel-based CPU, 64Gb Memory
Solution 1:[1]
Posting this answer in case it would save time for anyone landing on this post seeking to get answers to the same issue I was having.
DataGrip UI has two places where the list of visible tables can be filtered, and those filters are compound. First is a main filter next to Data Explorer:
The second place is under Data Sources and Drivers -> Schemas -> Object filter options.
Solution 2:[2]
Thanks to @aerial301 for this answer:
lifeTotal.textContent = +lifeTotal.textContent + 5
It works. I assume that the + in front of my Var lifeTotal is converting the DOM content targeted by the .textContent to a number, which let JS see 2 numbers instead of a string and the number 5.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | QRrabbit |
| Solution 2 | Jean-Yves TRAN |

