Not All Databases/Schemas Are Displayed by Default. Why?
There is one thing which makes DataGrip different from many other database tools: DataGrip doesn’t show all schemas and databases by default in the database explorer. In this post we’ll briefly describe why it’s designed like this and what you can do if this doesn’t suit your workflow.
The most important thing about DataGrip is that the essence of its work concerns database introspection. Introspection is the process where DataGrip loads the metadata for all the database objects and then uses this metadata for coding assistance and navigation.
By default, all schemas shown in the database explorer are introspected. So, you need to choose which schemas should be displayed and introspected. You can do this in the Schemas tab of the data source properties:
Or via the tiny button near the data source name in the database explorer:
In general, it’s logical that you want to see and introspect only the schemas you are working with. Behind the aspect of introspection, it’s convenient to see only what you need. Many databases have tons of schemas, but only a few of them may be needed at any one time. Those who work with these databases find this feature very useful :)
The most valuable thing is that we don’t introspect the schemas you don’t need. This saves you time and disk space. Again, we don’t know how big your schemas are and how many databases you have – we prefer not to make any assumptions.
Anyway, if you do want all of your database schemas to be introspected, just tick the corresponding checkbox:
In cases where the data source has schemas inside databases, the checkbox All Schemas should be manually ticked as well.
If you always want to see all databases and schemas, we have another handy setting: Show all namespaces. If this option is turned on, all databases and schemas will be displayed in the database explorer, but not introspected. Should you wish to introspect one of them, select it and click the Refresh button.
We hope this post clarifies the situation and provides you with the necessary workarounds.
The DataGrip team
Subscribe to Blog updates
Thanks, we've got you!
Introspection Level Auto-Selection
Back in 2015, I was the only DataGrip team member working on database introspectors. Since then, several of my teammates have followed suit with their own introspectors for various database management systems (DBMSs). The Oracle introspector, however, remains solely my project. The Oracle introsp…
Nextсloud Performance Hacks with EverSQL and DataGrip
Hi, I'm Pasha. In my everyday life, I'm a Developer Advocate for data engineering, but by night, I'm a geek. Like, a really geeky geek! I have used Linux since 2009 as my primary OS (BTW I use Arch). If possible, I always prefer to host everything I use. So if you decide to drop me an email at me@as…
Top 10 DataGrip shortcuts to empower your coding
We love shortcuts. They make coding faster and more efficient. But they are not always easy to remember. With that in mind, we’ve put together a list of our top-10 most useful DataGrip shortcuts. Execute statement: Cmd/Ctrl+Enter Click the statement or select the fragment of code that you want…
Working with source codes in DataGrip
Basics The source code of the object is the core part of the DDL script which is needed to create this object. In other words, the CREATE statement is not part of the object's source code. The source code is stored inside the database. The most common objects found with the source code are views,…