#1: When the query is optimized the actual values are not yet know when they come from another table. Btw, in TD14.10 there's a new feature "Incremental Planning" which will resolve such non-correlated Scalar Subqueries like hard-coded values.
My MIN/MAX subquery will not changed the result as it's supposed to be an additional condition.
#3: When you use a view as i described you will see hard-coded values within explain, so there's no need for "enhanced by dynamic partition elimination".
#1: When the query is optimized the actual values are not yet know when they come from another table. Btw, in TD14.10 there's a new feature "Incremental Planning" which will resolve such non-correlated Scalar Subqueries like hard-coded values.
My MIN/MAX subquery will not changed the result as it's supposed to be an additional condition.
#3: When you use a view as i described you will see hard-coded values within explain, so there's no need for "enhanced by dynamic partition elimination".
Dieter