nevermind. thank and Christian for the replies.<br><br><b><i>Max Rydahl Andersen <max.andersen@redhat.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <br>You got two replies already and you still want to argue if you have our <br>ears.<br>Either speak up or don't ;)<br><br>As I said my background is medical systems and I disagreed with the level <br>of dynamacity you referring to...<br>you take it from there.<br><br>/max<br><br>> sorry I don't see how Christian answer was serious brushing me off with <br>> few classes to insert into EAV. granted the way I landed this on you <br>> deserves such a reply but can we skip to the serious phase.<br>> well spotted that I am talking about a deep level of dynamic. Serveral <br>> domains not just the medical field have thousands of objects with <br>> subsets needed in different circumstances. some domains use domain
<br>> specific languages with runtimes to interpret content. There are many <br>> reasons why you can't map objects to tables at design time. There are <br>> many other reasons why you can't have a static domain model. I am not <br>> here to argue the problem but explore the solution with you.<br>> do I have your ears?<br>><br>> Max Rydahl Andersen <max.andersen@redhat.com> wrote:<br>> Christians answer was actually serious ;)<br>><br>> My background is medical systems and both HL7, GEPJ and the european<br>> DH<br>> has a great deal of genericity because the medical domain has it...but I<br>> don't see how it requires<br>> the level of dynamicity you are referring too.<br>><br>> /max<br>><br>>> very funny. I had similar skepticism until I worked in such domain. I<br>>> understand the issues surrounding such a model, I spent 15 years working<br>>> for Oracle. implementing it is not that trivial. there
is a real need<br>>> and I explain the details if I have more serious replies.<br>>><br>>> Christian Bauer wrote:<br>>> On Apr 30, 2007, at 9:48 PM, Iyad Elian wrote:<br>>><br>>>> alternative persistence model common in some domains like the medical<br>>>> domain. how do I go about it?<br>>><br>>> So data consistency and integrity is not important in the medical<br>>> domain and the EAV stuff is used as the main model for data<br>>> management? I can't believe that. EAV is just a synonym for "I don't<br>>> like to think about data management and schema evolution, therefore<br>>> let me break it right away in the design phase." Of course, it has<br>>> its uses but it's rare to see it applied properly.<br>>><br>>> Implementing an EAV pattern on top of Hibernate is trivial. Attached<br>>> some source you may use if you promise never to design a system with<br>>>
this that runs my pacemaker.<br>>><br>>><br>>><br>>> ---------------------------------<br>>> Ahhh...imagining that irresistible "new car" smell?<br>>> Check outnew cars at Yahoo! Autos.<br>><br>><br>><br><br><br><br>-- <br>--<br>Max Rydahl Andersen<br>callto://max.rydahl.andersen<br><br>Hibernate<br>max@hibernate.org<br>http://hibernate.org<br><br>JBoss a division of Red Hat<br>max.andersen@jboss.com<br></max.andersen@redhat.com></blockquote><br><p> 
<hr size=1>Ahhh...imagining that irresistible "new car" smell?<br> Check out
<a href="http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-">new cars at Yahoo! Autos.</a>