First of all, thank for your advice.
Certainly I got the field name wrong.
It is a customer_id field, not customer_name.
Anywayse I agree that domains can solve certain datatype problems.
I also appreciate your tip to reuse the domains declared.
However, my problem is a little bit different from what you
understood. I presented an inappropriate example and it seemd to have
confused you. Datatype standards files can be used to map logical
datatypes to physical datatypes. Of course, it can be combined with
domains. I think its main purpose is that you can derive any physical
models(SQL 2000, Oracle...) from a logical model without changing
datatype manually.
For example, let's say you have a domain, EmailType. Its logical
datatype is varchar(128).
When you derive a physical model for ORACLE, you want to map it as
varchar2(128). But at the same time, you want to implement it with
SQL server 2000, then you need to just keep it as varchar(128).
If you have created two datatype standard files for both database
types, then you can just link a corresponding datatype standards file
whenever you derive a physical model for a certain database type.
In that way, you don't have to worry about changing the domain
datatypes for different database server implementations.
Anywase, I have figured out myself why the problem was happening.
It seems like a bug or limitation of ERWin 4.0 evaluation version
(don't know which one is, though).
I have downloaded the newest version, ERWIN 4.1, and it does not have
the problem any more.
--- In ERWin-DB-Modeling@xxxxxxxxxxxxxxx, "Warren" <wcotton950@xxxx>
wrote:
> I suppose it's beside the point why you would want a customer_name
> field to be datatype integer. I'd expect it to be character.
>
> I don't know what you mean by a "datatype standard file." ERwin
uses
> a Domain Dictionary embedded in each model file. You access the
> Domain Dictionary under Model/Domain Dictionary.
>
> The easy way to set up a standard Domain Dictionary is to define it
> once in a blank ERwin file, then use Complete Compare to import the
> domains into whatever model you're working on.
>
> Domains are assigned a datatype. Then when you add an attribute to
an
> entity, you assign a domain to the attribute. ERwin automatically
> assigns the datatype of the domain to the attribute. You can change
> the datatype if you wish.
>
>.
To subscribe, send an email to:
ERWin-DB-Modeling-subscribe@xxxxxxxxxxxxxxx
To unsubscribe, send an email to:
ERWin-DB-Modeling-unsubscribe@xxxxxxxxxxxxxxx
Archives: http://groups.yahoo.com/group/ERWin-DB-Modeling/messages
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/VzvwlB/TM
---------------------------------------------------------------------~->
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/ERWin-DB-Modeling/
To unsubscribe from this group, send an email to:
ERWin-DB-Modeling-unsubscribe@xxxxxxxxxxxxxxx
Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|
