At 01:03 PM 20/06/2003 +0000, you wrote:

>The IBExpert shows the following plans:
>
>Plan
>PLAN JOIN (JOIN (MATRICULA NATURAL, ALUNO INDEX (RDB$PRIMARY3)),
>PARAM_PER INDEX (RDB$PRIMARY14))
>
>Adapted Plan
>PLAN JOIN (JOIN (MATRICULA NATURAL, ALUNO INDEX (INTEG_8)),
>PARAM_PER INDEX (INTEG_38))
>
>But the Pk of PARAM_PER is periodoano_paramper, which is
>a Char(6)!

INTEG doesn't mean integer, it means INTEGrity. What is weird about this
is that constraint names are showing up in a plan.

I tested to see whether the new thing in RC3 about named constraints was
maybe operating on a UNIQUE constraint, causing the constraint name to be
applied to the enforcing index.

But, no. The index got a RDB$ name.

So how does IBExpert manage to pull constraint names into a plan?

heLen