Hi,
>What about even shorter notatoin, something like
>
>TurbineU_PK
>TurbineR_PK
>TurbineG_PK
>TurbineP_PK
>TurbineUGR_FK_U
>TurbineUGR_FK_G
>TurbineUGR_FK_R
>TurbineRP_FK_R
>TurbineRP_FK_P
>
>+ namespace safe
>+ no ambiguity
>+ no truncated names
>
>Thoughts?
Index names and other database object names related to tables need only
be unique in the first 18 chars. Therefore, they _could_ be assigned
serial numbers (ie. IDX_00456). The application _never_ has to refer
to them by name anyway. However, they should *not* be generated this
way because error messages typically include the database object name
(i.e. the index name) and the index names should make it clear to a
_human_viewer_ what the index was.
So...
1. It really doesn't matter how the generator creates index names
except that they should be unique in 18 chars and...
2. relatively mnemonic.
When I design databases, I use the rule that table names may be longer
than 18 chars on occasion, but that every table name should be unique
in the first 14 chars. This gives me plenty of room to make my index
names.
Someone thought I was suggesting that the table names be changed
*again*. Not so. I was simply suggesting that we validate that all
of the databases we care about will support the use of long table names
even if we force ourselves to make each table name unique in the first
14 (or 18) characters.
Stephen
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
