Thanks Chad;


The issue I have is that I am trying to implement enumerations as type codes, 
meaning: in the application I use codes like 0,2,3 which will then map to 
descriptions such as, open, close, pending, etc. Use of lookup tables is a well 
known practice that allows users to add rows to these tables as needed. See, 
the application uses the code (which normally a number) to find the human 
readable code which code be Open, Close, etc. not the other way around. Also 
these lookup tables can have 1000's of rows, in fact I have few that has 
hundereds. After some search I saw the best way to implement this is as tabels, 
which means in UML/hibernate as entities for couple reasons, correct me if I am 
wrong:



- Current enumeration implementation has the problem we went over that won't 
allow the use of numbers as identifiers.



- Enumeration classes are not persisted to the database as tables (that is what 
I can see from the generated code and schema and data structure) thus can't be 
edited in the future to add more enumeration or lookup rows without having to 
go back everytime and update the model to add a new enumeration value specially 
for large number of enumerations. If enumerations are not persisted to the 
database this probably means they have to be pre-loaded in memory which for 
hundereds or thousands of enumerations can be an issue specially if I have 10's 
of these enumeration types which I do.



- I also seen another rational for using type code that has to do with being 
language-independent compared with the character-based identifiers. 



= In fact it would be nice if the entity implementation in AndromDA was such 
that it allows a second stereotype (lookup or enumeration) so that it can take 
a UML enumeration lietral list and generate a table with this initial list as 
set of rows in the database, thereafter one can either update this enumeration 
list and regenerate the tables or just update the tables directly.



Just a suggestion. In the mean time, I believe the enumeration modeling in 
hibernate/andromda can be used for well known set of character based literals 
(not lookup codes).



Again, any remarks that can help either confirm my observations or correct them 
are greatly appreciated.



Regards



Safaa
--
Safaa Hashim
_________________________________________________________
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3300#3300
Posting to http://forum.andromda.org/ is preferred over posting to the mailing 
list!


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Andromda-user mailing list
Andromda-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to