Data modelling domain attributes

[skiwi]

I want to use domain attributes for the data type in a column definition in my table classes.

Can anyone point me to the documentation on how to do this,
or describe how they achieve.

For example I might have the following domains

domain name	data type	len
code	nvarchar	6
identity	bigint
name	nvarchar	100
description	nvarchar	200

I want to use and see the domain name when I am working with models, but have the physical data type instantaiated when I create the actual database and tables, or update them.
Obviously this have advantages for documentation understandability and maintainability.

Any and all advice gratefully accepted

Simon

[«Midnight»]

EA does not support data domains as yet.

This has been a long-standing limitation of the EA data model paradigm. The root cause does not lie with Sparx though. It dates back to the metamodel that they have used, which did not recognize the concept of data domains. At the time there was little else in the way of UML data model frameworks in wide publication.

Perhaps in future.

Sorry the news is not better,
David

PS: You could always make a feature request to Sparx. They've had this requested before, but to no avail as yet. If enough feature requests (from enough distinct users) come it perhaps the priority balance will come around to a more favorable position.

[skiwi]

I have submitted this as a feature request

viz

Please see http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1246399152/1#1

When creating data models it is useful to maintain a list of domain names that describe attributes.

These domain names then have the physical database data types etc ascribed to them rather than to model attributes.


This feature request is to support both simple and  complex domain names.

Simple domain types are a one to one match to an attribute.

Complex domain types  represent several attributes (eg address (street, suburb, city), email address (domain and user name), phone number (country code, area code, subscriber number) .
They can be generated by suffixing a name to an attribute name.

thankyou

[Oliver F.]

There is a way around that limitation.
Either you write an addin which is called from the template (%EXEC_ADD_IN) or you run a script after the transformation which fixes the datatypes.

This is how we circumvented it. However I vote for this feature request.

Oliver