Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
|
|
91 KB
You can use "show search_path" to see the session current path. Looks like restoring windows also doesn't set the previous schema, even though the schema shows the old one.
We added support to show the first schema in the search_path, but did not add support to change schema or change search_path. So, when you clone or restore the schema should not clone the previous, or restore the previous schema.
I've fixed it so that the query window will show the correct search_path of the connection with restoring and cloning.
Issue #7819 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 12.0.0-rc-23-16 |
| No time estimate |
1 issue link |
relates to #344
Issue #344PostgreSQL: Add the ability to change the schema context. |
You can use "show search_path" to see the session current path. Looks like restoring windows also doesn't set the previous schema, even though the schema shows the old one.
We added support to show the first schema in the search_path, but did not add support to change schema or change search_path. So, when you clone or restore the schema should not clone the previous, or restore the previous schema.
I've fixed it so that the query window will show the correct search_path of the connection with restoring and cloning.