| Subject | Re: Why does the optimizer choose NATURAL for this tiny table? |
|---|---|
| Author | Dmitry Yemanov |
| Post date | 2014-11-13T19:09:39Z |
13.11.2014 14:39, Svein Erling Tysvær wrote:
P.ICD10 and T.ICD10 differ. ICD10 is an expression inside T, so its hard
to say what the resulting data type is.
Dmitry
> D1) ON p.icd10 = t.icd10Interesting. The only possible explanation is that the datatypes for
>
> These change the plan to:
> PLAN JOIN (MERGE (SORT (JOIN (P NATURAL, G INDEX (I_ICD10_GRUPPE_ICD10))), SORT (JOIN (T KID INDEX (U_NPR_KRG_ID_FNRK), T N INDEX (I_NPR_KRG_ID), T T INDEX (I_NPR_TILSTAND_ID_NPR)))), I INDEX (PK_ICD10))
P.ICD10 and T.ICD10 differ. ICD10 is an expression inside T, so its hard
to say what the resulting data type is.
Dmitry