hum I think join-subclass is the answer to my problem.. correct me if
I'm wrong.

On 29 avr, 11:41, graphicsxp <graphic...@googlemail.com> wrote:
> Hi,
>
> I have an issue due to some poorly design database (which I can't
> change now).
>
> I want to have 3 classes :
>
> Person ,
> Employee which inherits from Person
> Analyst which inherits from Person as well.
>
> In the database there are 3 tables :
> [Person] {PersonId, Fullname}
> [Employee] {EmployeeId, PersonId, Salary}
> [Analyst] {AnalystId, PersonId, AnalystJob}
>
> Ideally, these 3 tables should have been regrouped into one single
> table and using a discriminator i would have been able to create the
> appropriate class.
>
> Unfortunately I have to keep these 3 tables, but I would really like
> to avoid having to create 3 mapping files. How can I have one mapping
> file for the Person table and then creates appropriate classes ? Or is
> it just not possible ?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to nhusers@googlegroups.com
To unsubscribe from this group, send email to 
nhusers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to