AE does not allow non-unique Ordinal numbers

Description

see https://openehr.atlassian.net/browse/SPECPR-101

There are 2 issues in AE

1. The use of the Oridinal code number as primary key within OrdinalTable, forces unique=true and causes VB to raise an error. This can be worled around by making the primaryKey multiple column based in both ordinal code and atCode

2. The successfully saved archetype with non-unique Ordinal cannot be read because of an error message from the Eiffel parser - see screenshot.

Environment

all

Reporter

Ian McNicoll

Labels

None

Components

Affects versions

Priority

Major
Configure