Error "The specified object could not be found" after database recreation

[maxfd3v]

Description

When a database is recreated while pgAdmin has an open connection to it, attempting to view or edit data from a table results in the error "The specified object could not be found" instead of displaying the requested data. This issue occurs even after refreshing the table; only refreshing the entire database resolves it, which is inconvenient and disrupts workflow.

Steps to Reproduce

• Open pgAdmin and connect to a database.
• Open the schema browser for the database.
• Recreate the database (e.g., drop and create it).
• Right-click a table in the tree view and select "View/Edit Data."
• Observe the error: "The specified object could not be found."

Error
The specified object could not be found

Expected Behaviour

Ideally pgAdmin should automatically handle database recreation and allow access to table data without manual intervention. Worst case it should refresh correctly on doing a refresh on the table

Workaround

Right-click the database in the object browser, and select "Refresh." This is time-consuming, especially in environments where databases are frequently recreated.

Desktop (please complete the following information):

• OS: [Ubuntu 22.04.5 LTS, Linux-6.8.0-57-generic-x86_64-with-glibc2.35]
• Version: [9.2]
• Mode: [Desktop]
• Package type: [DEB]
• Python Version: 3.10.12

Additional context
Existing open table view windows will refresh after prompting about db connection being dropped.