LDM - PDM Generation Options : index naming

[Ndy]

Hi, i can't find how to do it with PD15

When i want to convert my LDM to PDM, in the Detail tab, we can
spécified the naming convention for PK AND FK for exemple.

EX:

PK index name : PK_%TABLE%
FK index name : FK_%REFR%

The probleme is when you have 2 tables : MY_TABLE_NAME_IS_VERRY_LONG
and MY_TABLE_NAME_IS_VERRY_LONG_2

So the PK index name become for both PK_MY_TABLE_NAME_IS_VERRY_LONG
wich will cause error because of constraint name uniqueness

how can we specified a convention while creation/updating the PDM
(something like PK_MY_TA_NA_IS_VE_LO and PK_MY_TA_NA_IS_VE_LO_2)

[rkkier]

I just took a look at the variables available (search the help file
for PDM variables) and I don't see anything that looks useful but you
might find something there. There's a REFRNO variable on references
which might help if you had the problem elsewhere, but you'd need
something at the table level for the primary key.

There is a model check built in for this (Table Key | Key Name
Uniqueness) that has an autocorrect, so the easiest way to fix it is
immediately run a model check (you can turn off everything else if you
want), highlight the results and tell it to fix them.

[Mark Brady]

Post by rkkier
I just took a look at the variables available (search the help file
for PDM variables) and I don't see anything that looks useful but you
might find something there.  There's a REFRNO variable on references
which might help if you had the problem elsewhere, but you'd need
something at the table level for the primary key.
There is a model check built in for this (Table Key | Key Name
Uniqueness) that has an autocorrect, so the easiest way to fix it is
immediately run a model check (you can turn off everything else if you
want), highlight the results and tell it to fix them.

This is where you'd employ a glossary.

In it you can define that:

TABLE be replaced with TA
VERRY be replaced with VE

etc.

a complete glossary will make your names consistent and short.

[Ndy]

Post by Mark Brady

Post by rkkier
I just took a look at the variables available (search the help file
for PDM variables) and I don't see anything that looks useful but you
might find something there.  There's a REFRNO variable on references
which might help if you had the problem elsewhere, but you'd need
something at the table level for the primary key.
There is a model check built in for this (Table Key | Key Name
Uniqueness) that has an autocorrect, so the easiest way to fix it is
immediately run a model check (you can turn off everything else if you
want), highlight the results and tell it to fix them.

This is where you'd employ a glossary.
TABLE be replaced with TA
VERRY be replaced with VE
etc.
a complete glossary will make your names consistent and short.

where can you define the glossary ?

[rkkier]

Tools | Resources | Conversion Tables allows you to create the
abbreviation file. It's just a CSV file so you can also edit it in
Excel once you have it started. Ours has over 5000 entries so finding
duplicates and ensuring consistency is a little easier in Excel than
in the built in editor.

Once you have the conversion table setup you specify it in Tools |
Model Options | Naming Conventions