-
-
Notifications
You must be signed in to change notification settings - Fork 119
App is unusable after reconnecting to a PostgreSQL database next time #540
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
What happened?
Context
- User connects to a PostgreSQL database.
- The active schema is xxx, not the default schema (
public) - User opens a table, and data is loaded successfully during that session.
- User restarts app.
Actual behavior and error:
- After selecting the saved connection, the app displays the error dialog
Query execution failed. The query looks like:
ERROR: relation "yyy" does not exist
LINE 1: SELECT * FROM "yyy" LIMIT 1000
^ (SQLSTATE: 15)
Issue: The actual query does not include the schema name.
The correct query should be
SELECT * FROM "xxx.yyy" LIMIT 1000;- Clicking the OK button does not close the error dialog. As a result, the app is unusable. This is a critical error, a terrible UX.
Steps to reproduce
No response
Expected behavior
Expected behavior: User can use the app normally after restarting app and open a saved connection to connect to the PostgreSQL they connected before.
Database type
PostgreSQL
TablePro version
0.26.0
macOS version & chip
26.3.1 / M3 Pro
Screenshots / Logs
N/A.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working