Problem
When generating ER diagrams for large-scale databases or schemas containing many partition tables (e.g., PostgreSQL table partitioning), the diagram becomes highly cluttered and difficult to navigate. This is because all partition child tables are drawn flatly alongside main tables.
It would be extremely helpful to have a way to exclude specific tables (such as partition child tables or system metadata tables) from the generated ER diagram.
Proposed Solution
Add an --exclude-table <pattern> option to the CLI (erd build command).
This option would allow users to specify glob-like patterns (e.g., sensor_logs_p*, or comma-separated lists like sensor_logs_p*,audit_logs) to filter out matching tables during the preprocessing phase.
Current Status
I have already implemented this feature locally and verified that it works as expected (all existing and new tests pass). Since direct pull requests to this repository seem to be restricted at the moment, I have pushed the working code to my fork repository:
I would appreciate it if you could review the changes and let me know if you would like me to open a Pull Request (once restrictions are lifted) or if you want to pull the changes directly from my fork.
Problem
When generating ER diagrams for large-scale databases or schemas containing many partition tables (e.g., PostgreSQL table partitioning), the diagram becomes highly cluttered and difficult to navigate. This is because all partition child tables are drawn flatly alongside main tables.
It would be extremely helpful to have a way to exclude specific tables (such as partition child tables or system metadata tables) from the generated ER diagram.
Proposed Solution
Add an
--exclude-table <pattern>option to the CLI (erd buildcommand).This option would allow users to specify glob-like patterns (e.g.,
sensor_logs_p*, or comma-separated lists likesensor_logs_p*,audit_logs) to filter out matching tables during the preprocessing phase.Current Status
I have already implemented this feature locally and verified that it works as expected (all existing and new tests pass). Since direct pull requests to this repository seem to be restricted at the moment, I have pushed the working code to my fork repository:
I would appreciate it if you could review the changes and let me know if you would like me to open a Pull Request (once restrictions are lifted) or if you want to pull the changes directly from my fork.