Jitendra,
thanks for responding. Details table is as I said just to hold versions.
Consider a master table called Plan. it has a primary key planid.
Now there is PlanDetails table, which has primary key as (planid, planeffdate) This is required as the same plan (with same planid) can be closed and reopened any number of times over a period of time. So, whenever a plan is closed a corresponding column in the Details table will be updated. Also, when a plan is opened again one more record will be inserted into PlanDetails table, with new Planeffdate (plan effective date). Details table also has lot of other fields.
But in the domain model, we just want to use one class to store both master and details tables. considering its a 1-many relationship how can I creating mapping for a single class. If it is a 1-1 then I could have used <join> tag? Any help would be rated very high!
Thanks
K
|