[nhusers] Re: Table per concrete class, legacy db, and association

I didn't know that attribute existed! Thanks a lot. And yes, it's a table per class hierarchy. I said per concrete class because of the approach I was applying: "having 2 classes in separate tables, but the tables are the same one, and using implicit polimorphysm" Thanks a lot again! On 16 feb, 0

[nhusers] Re: Table per concrete class, legacy db, and association

the following somewhat abbreviated mapping work btw the strategy you described is called "Table per class hierarchy"