[Bug]: Database Export/Dump Context Switching Failure in Multi-Database Environment

[cyrdodi]

Describe the bug

When attempting to dump a database or export a table to CSV in an environment with multiple databases visible under the same connection, the application fails to scope the query context to the selected database. Instead, it improperly references or executes the export command against a different database (typically the first database alphabetically or historically selected, e.g., cat_playroom), resulting in a 1146 (42S02) error.

Expected Behavior

The application should correctly scope the export operation to the active target database (web_opd_backend) and successfully generate the dump or CSV file.

Actual Behavior

The export fails immediately with the following database error, indicating it is looking for the target tables inside the wrong database context (cat_playroom):

Export failed: error returned from database: 1146 (42S02): Table 'cat_playroom.document_categories' doesn't exist

Environment Details

• Version: V.0.13.2
• Opertaing System: CachyOS (arch)
• Database Engine: MySQL
• Context: Multiple databases loaded in the sidebar explorer.

Additional Notes
This issue is consistent and affects both the full database schema dump feature and individual table CSV exports.

It appears the application does not explicitly execute a USE target_database; statement or fully qualify table names with the correct database prefix during the export pipeline runner.

To Reproduce

• Open Tabulars and connect to a MySQL instance containing multiple databases (e.g., cat_playroom, web_opd_backend, etc.).
• Select a database other than the first one (e.g., select web_opd_backend).
• Open the Dump Database dialog (or attempt to export a specific table to CSV).
• Ensure "Structure (DDL)" and "Data (INSERT)" are checked, then click Export.

OS Version

CachyOS (Arch)

Tabularis Version

V0.13.2

Relevant Log Output

Export failed: error returned from database: `1146` (`42S02`): Table 'cat_playroom.document_categories' doesn't exist

[debba]

Thanks for the report and the clear analysis, the table-not-found error pointed right at it.

The dump and the export were running against the connection's primary database rather than the one you selected, which is why it looked for the tables in the wrong database. This should be fixed in #346: both now scope to the selected database, and the dump dialog also reloads that database's tables when it opens.

The fix will be included in the next release. If you want to test it beforehand, see #346.