Subject | RE: [firebird-support] Why PLAN token is not allowed after ORDER BY? - Email found in subject |
---|---|
Author | Leyne, Sean |
Post date | 2012-06-03T19:06:49Z |
> We create indexes programmatically and we we generate their names basedIf that is the case, why is the name gibberish?
> on their definition, such the columns they index.
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