Enhancement: Add a Schema-Aware Table Tabs Display Preference #3431

Problem

When working with multi-schema databases under the same database connection, TablePro keeps table tabs from different schemas visible in the same workspace.

For example, in a multi-tenant database where each tenant has its own schema, opening the same table across multiple schemas can result in duplicate tabs that are difficult to distinguish and manage.

Example scenario:

1. Open the orders table from tenant_a.
2. Switch to tenant_b within the same database connection.
3. Open the orders table from tenant_b.
4. The orders tabs from both schemas remain visible simultaneously.

This can cause confusion when switching between tenants, especially when tables share the same names but contain different data.

Although TablePro now displays the schema name before each table name, this does not fully solve the problem. When working with databases containing many schemas and open tables, the workspace can accumulate a large number of tabs, creating visual clutter and making navigation confusing.

Proposed Solution

Add a user preference in Settings to control how table tabs are displayed when switching between schemas within the same database connection.

The setting should provide the following options:

• Show tabs from all schemas (default): Preserve the current behavior, displaying open table tabs from all schemas in the same workspace.
• Show tabs only from the selected schema: Display only the tabs belonging to the currently selected schema, while keeping tabs from other schemas open in the background and restoring them when switching back.

Configuration Scope

Ideally, this preference should be configurable per database connection, allowing developers to choose different behaviors for different connections. If this does not fit TablePro's existing settings design, a global preference would also be acceptable.

Expected Behavior

• Switching schemas should update the visible table tabs according to the selected preference.
• In schema-specific mode, tabs belonging to other schemas should be preserved rather than closed or discarded.
• Switching back to a previously selected schema should restore its previously opened table tabs and their associated state, where supported by the existing tab implementation.
• The default behavior should remain unchanged to avoid disrupting existing users.

Benefits

• Reduces tab clutter when working with databases containing many schemas.
• Makes it easier to focus on the currently selected tenant or schema.
• Reduces the risk of confusing tables with identical names across different schemas.
• Preserves existing work without requiring separate database connections for each tenant.

Alternatives Considered

No alternatives considered.

Platform

macOS

Related Database Type

MySQL / MariaDB