I am in the process of reverse mapping a database into generated classes. I came across an issue with joiner tables that have one or more extended properties in them.
- Person table
- Family joiner table
Each person can have multiple links to other people in the person table through the Family joiner table. The Family joiner table also contains a few extra fields to define the relationship type, marital status, related by marriage, etc.
Since that joiner table has extra fields beyond the joiner id's, the reverse mapper wants to make it a class rather than just a joiner. Is that standard practice? Or is that something that folks with experience would recommend handling a different way either at the database level or in the persistant classes?