Fix DataGrip Schema Navigation – Databases or Schemas Not Visible

In this tutorial, you'll learn about Fix DataGrip Schema Navigation. We cover key concepts, practical examples, and best practices.

You connect a data source in DataGrip. The connection test passes, but the Database Explorer shows almost nothing — maybe one schema, no tables, or only a subset of databases. You know the server has hundreds of tables, but DataGrip isn't showing them.

Wrong ❌

📁 data sources
  📁 mydb@localhost
    📁 information_schema

That's it. No public, no app, no analytics. You click Refresh (F5) — nothing changes. You reconnect — still empty.

You expected:

📁 mydb@localhost
  📁 information_schema
  📁 public
    📁 users
    📁 orders
    📁 products
  📁 app
  📁 analytics

Right ✅

Introspection scope fix:

1. Right‑click the data source → Properties
2. Go to Schemas tab
3. You'll see a list of tickboxes — by default, only information_schema is ticked
4. Tick the schemas you want visible: public, app, analytics, etc.
5. Alternatively, click All schemas to show everything

Also check the General tab:

Look for Introspect using JDBC metadata vs Introspect using same connection:

• JDBC metadata — uses driver metadata (faster, may miss objects)
• Same connection — uses SELECT queries (slower, complete)

Switch to Same connection if schemas are still missing after ticking.

Refresh after changes:

Right‑click the data source → Refresh (Ctrl+F5). Full tree appears:

📁 mydb@localhost
  📁 information_schema
  📁 public
    📁 users (24 columns)
    📁 orders (18 columns)
    📁 products (11 columns)
  📁 app
  📁 analytics

Root Cause

DataGrip limits introspection to selected schemas to keep the tree responsive. On large databases with many schemas, the default selection may include only system schemas. Users expect the tree to show "everything" automatically.

Prevention

• After creating a new data source, always visit the Schemas tab and tick the relevant schemas.
• For development databases, tick All schemas once — DataGrip remembers the selection.
• Use Filter by name in the Schema tab if the list is long.
• Share schema visibility settings via Data Source → Export → To XML for team consistency.

Common Mistakes with schema navigation

1. Using return to exit a function early instead of wrapping a pure value in the monad
2. Mixing let bindings with <- bindings in do notation, producing type errors
3. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors

These mistakes appear frequently in real-world DATAGRIP code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Optimise DataGrip navigation in the DodaTech DataGrip Efficiency course.