Sean, you nailed the reason on the head - the FB restriction on index
names. In fact, on SQL Server we have pretty index names :) Unfortunately,
we didn't have the resources to spend in prettyfying the index names at the
time. At this point it's even harder to do this because of upgrade
scenarios.

Thanks,

Alec

On Sun, Jun 3, 2012 at 1:06 PM, Leyne, Sean <Sean@...>wrote:

> **
>
>
>
> > We create indexes programmatically and we we generate their names based
> > on their definition, such the columns they index.
>
> If that is the case, why is the name gibberish?
>
> You could create an index which has the name(s) of the source fields (ie.
> "PK_PhysicalCopy.ID" or "FK_PhysicalCopy.CopyID" or "PC.ISDIRTY"), rather
> than the GUID-like non-names which you currently use.
>
> Yes, there is a limit to the length of an Firebird index name, but you
> could come up with an algorithm which would be able to shorten the names as
> appropriate. For example an compound index of
> COPY_CLASSIFICATION."CLASSIFICATION_CODE" and
> COPY_CLASSIFICATION."LABEL_CLASSIFICATION_CODE" could be named
> "COPY_CLASS.CLASSIF_LABELCLASSIF".
>
> Sean
>
>
>


[Non-text portions of this message have been removed]