Book a Demo

Author Topic: Code & DB datatypes uniqueness - bug or feature?  (Read 11328 times)

Krzysztof Swiatkowski

  • EA User
  • **
  • Posts: 76
  • Karma: +0/-0
  • Understanding is a three-edged sword
    • View Profile
Code & DB datatypes uniqueness - bug or feature?
« on: March 28, 2008, 03:11:42 am »
Hi,

I have a problem with transformations and Code Datatypes and Database datatypes windows (Settings menu). Because datatypes definitions are used in transformations i have a problem with having a unique constraint on datatype.
I would like to define several Common types that would map to string type. Example could be class TaxPayer{Tax ID: TIDCode, Name: Text, Description: Memo}.
There I cannot define mappings TIDCode->string, Text->string, Memo->string.
I think there should be unique constraint on Common Type which is logical because I cannot have two definitions for Text, but not on Data type because many Common Types can map to string.
The same problem or even worse is present in DB datatypes. I cannot define mappings to varchars of different lengths.

I would like to transform conceptual diagram with abstract/common datatypes to both programming language and database structure, but with this constraint it is very hard to do.

So the question from topic-> is it a bug that can be fixed or a feature to make my life harder :)

Regards
Kris
If I put you finger in the eye
then you have finger in the eye
and I have finger in the eye
but it's not the same