A
Andy
Hi All!
How do preserve the same field order of a composite primary key in a
logical model and physical model?
I am trying to use Visio Architect addition to generate DDL.
I've found when I have a composite key on a table Visio generates the
primary key with fields in reverse order.
MyTable:
report_period PK
party_id PK
address_id PK
Then PK will be generated as
alter table " MyTable "
add constraint " MyTable _PK" primary key (address_id , party_id,
report_period)
First, There are some reasons behind a report_period should be the
first field in PK.
The second, many tables have report_period as PK
Is there way to preserve the same field order in a table model and a
composite primary key?
(of course it is possible to change order in the model, but I prefer
to have the same order in logical and physical model)
Thank you
How do preserve the same field order of a composite primary key in a
logical model and physical model?
I am trying to use Visio Architect addition to generate DDL.
I've found when I have a composite key on a table Visio generates the
primary key with fields in reverse order.
MyTable:
report_period PK
party_id PK
address_id PK
Then PK will be generated as
alter table " MyTable "
add constraint " MyTable _PK" primary key (address_id , party_id,
report_period)
First, There are some reasons behind a report_period should be the
first field in PK.
The second, many tables have report_period as PK
Is there way to preserve the same field order in a table model and a
composite primary key?
(of course it is possible to change order in the model, but I prefer
to have the same order in logical and physical model)
Thank you