Preventing new primary key when generating DDL dia

[pstein]

Assume I have a UML class diagram.
One of the attributes of classs "aaa" is "myid" which should be the primary key in a corresponding DDL diagram.

However when I transform the current UML class diagram into a DDL diagram then always automatically a new attribute (=column) is invented/created: PK_myclass(INTEGER) instead of using the intended myid as primary key.

How can I prevent the auto-generation of a new field/column and tell EA to use "myid" as primary key in the target DDL diagram?

Peter

[philchudley]

There are two possible ways:

1) Modify the DDL generation scripts, the way I did it was to assign a tagged value with the name PK (value Yes) and attach this to the attribute to the primary key (or keys)

2) Name the primary key attribute ClassID, then this attribute will be the primary key

Cheers
Phil

[pstein]

Hello Phil,

thank you, but some questions:

ad 2.) Do I really have to rename the primary key attribute to "classID" or did you mean to enable somewhere (where exactly ?) a checkbox with the property "classID" for the primary key attribute "myprimkey"?

ad1.) How do I modify the (default) DDL generation script? Where can I find it at all?

Peter

There are two possible ways:

1) Modify the DDL generation scripts, the way I did it was to assign a tagged value with the name PK (value Yes) and attach this to the attribute to the primary key (or keys)

2) Name the primary key attribute ClassID, then this attribute will be the primary key

Cheers
Phil