Selecting Tables for DataGrip Diagram

>Even if I use the context menu for a single table, it shows all the related tables, which is often still way more than I want.

Works for me:

It could be that all the tables have relations between them, in which case the table would be shown even if it is not selected to be displayed. See related issue: https://youtrack.jetbrains.com/issue/DBE-532 , https://youtrack.jetbrains.com/issue/DBE-2718

There are foreign-key relationships, yes -- I definitely want to be able to select the entire set of tables and not include every other table that has is linked through foreign keys.

Neither one of those issues directly matches what I'd like -- full control over tables included. They each talk about controlling the depth. Although I suppose the existing selection plus depth:0 would let me get what I'm looking for?

Hi @Geoffrey Wiseman,

have you find a solution?

Crescenzo 

While it's been almost 8 years since this thread was created and there were many improvements made throughout this period of time, may I know what is your current use case with diagrams and what can we do about it to improve it?

@Aleksandr Molchanov

Thank you so much for your answer and help.

Currently, by clicking on two tables and selecting "show diagram" from the contextual menu, the complete diagram is displayed, while I would like to see the diagram only for these two tables. I have a DB with 350 tables and it is very complicated to navigate the diagram

Crescenzo 

There's currently no way to exclude the referencing tables before generating the diagram. You can remove them upon having the diagram. We have a feature request for such cases.

However, if your concern is the space occupied by the diagrams due to having to many objects in it, I'd suggest the following tip which should optimize the space taken by your diagrams.

Let me know if you have questions regarding this matter.

Let me be clear about what the issue is since you guys don't seem to understand. I have a set of tables that i want to know how they relate to each other. When I select those tables to show in a diagram, all related tables to those tables are also displayed. In what universe is this useful to anyone? I selected what i want to see. Why in the hell are you showing me all other related tables. What kind of decision is that being made for me? It's like me asking you to pick a number between 1 and 10 and you listing of all even numbers. Wherte is the logic or even common sense in that? This issue is 8 years old. How the hell are we still here?!

Alternatively, you can copy the selected table to a temporary database or schema and then view the schema diagram from the new database. This approach keeps the original database intact while allowing you to analyze the schema separately.

Crescenzo My workaround is that I don't use this DataGrip for database diagrams at all. I make database diagrams using other tools, because DataGrip's diagrams don't work the way that I want them to work.

Diagrams to me are a form of communication – which means that I want to control the message I'm making. Typically i'm working with relational databases that have many foreign key relationships, but when I want to talk about a few tables, I want those tables on a diagram, not every other table they're related to. 

Since DataGrip's diagram feature doesn't seem designed for that purpose, I don't use it, and I use things like dbdiagram.io instead.  If DataGrip's diagramming features were to evolve to give me more control, I might try it again.