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
Since change #52547, users are not able to use the global temporary plan_table because the explain statement now qualifies the plan_table with the current schema. In the case of the global temporary table, qualification is not necessary. Here is an example of how it is qualified:
EXPLAIN PLAN SET STATEMENT_ID = 'de8b07319c14ec249b4e-7' INTO DB_LEFT1.plan_table FOR SELECT * FROM DB_LEFT1.TBL01
This is how it should look:
EXPLAIN PLAN SET STATEMENT_ID = 'de8b07319c14ec249b4e-7' INTO plan_table FOR SELECT * FROM DB_LEFT1.TBL01
This not only affects the explain but affects the extraction and deletion of explain data from the global temporary plan_table.
The user sees the following messages:
|
|
50 KB
To explain to the global temp plan table. the user just needs to add "PUBLIC" and "PLAN_TABLE" to the explain schema and explain table respectively. Ideally, we should eventually fix this by either adding a check box or checking the current create explain table checkbox and explain schema field to see if they are empty.
Issue #15444 |
| New |
Completion |
| No due date |
| No fixed build |
| No time estimate |
To explain to the global temp plan table. the user just needs to add "PUBLIC" and "PLAN_TABLE" to the explain schema and explain table respectively. Ideally, we should eventually fix this by either adding a check box or checking the current create explain table checkbox and explain schema field to see if they are empty.