adrian_star
Member²
Hello,
I would like to propose an enhancement to the “Objects” window in PL/SQL Developer.
Objects → Tables → [Table Name]
The tree structure organizes related objects into separate subfolders such as:
For tables with multiple related objects, this becomes repetitive and time-consuming.
This node would display:
Tables
└── ORDERS
├── Columns
├── Primary Keys
├── Foreign Keys
├── Indexes
├── Triggers
├── Constraints
└── All
Selecting “All” would immediately show:
The current model requires multiple expansions per table, which:
An “All” node would:
This would be a small UI addition with high practical value.
Thank you for considering this enhancement.
Best regards,
Adrian
I would like to propose an enhancement to the “Objects” window in PL/SQL Developer.
Current behavior
When browsing a table in:Objects → Tables → [Table Name]
The tree structure organizes related objects into separate subfolders such as:
- Primary key
- Unique keys
- Foreign keys
- Indexes
- Triggers
- etc.
For tables with multiple related objects, this becomes repetitive and time-consuming.
Proposed enhancement
Add an additional node under each table: “All”This node would display:
- All related objects (except columns)
- In a single consolidated list
- Without categorization by type
Tables
└── ORDERS
├── Columns
├── Primary Keys
├── Foreign Keys
├── Indexes
├── Triggers
├── Constraints
└── All
Selecting “All” would immediately show:
- PK_ORDERS
- FK_ORDERS_CUSTOMER
- IDX_ORDERS_DATE
- TRG_ORDERS_AUDIT
- etc.
Benefits
This would allow developers to:- Quickly understand the full structure of a table
- Review all related objects at once
- Reduce excessive tree expansion
- Speed up schema analysis and onboarding
- Improve navigation efficiency
Business and productivity justification
In real-world enterprise environments:- Tables frequently have many related objects.
- Developers often need a quick structural overview.
- During debugging, performance tuning, or refactoring, rapid inspection is critical.
The current model requires multiple expansions per table, which:
- Increases navigation time
- Adds unnecessary interaction steps
- Slows down exploratory analysis
An “All” node would:
- Improve usability without removing the existing logical grouping
- Provide both structured and consolidated views
- Enhance productivity for daily development tasks
This would be a small UI addition with high practical value.
Thank you for considering this enhancement.
Best regards,
Adrian