I would like to know what is the reason for modeling the demographics of a party in the CLDM, FSLDM with the posible values already set in the DEMOGRAPHIC VALUE entity vs creating a column in the PARTY DEMOGRAPHIC HIST like Party_Demographic_Val VARCHAR(50) and put any value in there. Maybe similar to FEATURES in the FSLDM.
Hi, The Party Demographic Hist entity allows storage of specific values in the Party_Demog_Val Field.
For example: The Demographic Item of the Party is Income. The Income range is $40000 to $60000 and the specific income of the Party is $45000. So, The range is associated with Demographic Item in the Demographic Value Entity and the actual income is associated with the Party in the Party Demograpchic Hist entity.
Thanks Aravind, and you 're right, the FSLDM model include the Party_Demog_Val attribute, but the CLDM model (version 9.1) does not include this attribute. Do you know any reason from the modeling point of view for doing so?
I am new to Teradata and very much interested to know CLDM and FSLDM. I can interpret it as a logical data model. If you can explain whats the purpose of the models and where can I see them, will help me a lot.