We have a need to create a single CustomerEntity, but have the source data come from 2 Customer tables. I have a CustomerA table, but it has an extension table CustomerB. Not a great design, but it's in the legacy system so we have to deal with it.

So basically much like a TypedList, but with the richness and updateability of an Entity.

If this is not possible, would it be possible to create a CustomerEntityA and a CustomerEntityB and then 'partial class out' a single Customer?

One idea would be to base the Customer domain model on CustomerA, then create partial class Fields in CustomerA which talks to CustomerB. (Anyone remember what the name of the pattern is for this?)

Ideas?

I remember asking something similar on version 2.0 and the answer was no. Unless something has changed in version 2.5 i think your best bet is to create a composite class that wraps the two entities and manages interaction with the underlying data.

Would be interested to hear other view on the subject. What would others do?

Some options/hints:

1. Add _entityA _properties that indeed map to _entityB _fields using "Fields on related fields" (Designer) or by code (userCodeRegion or partial classes). So Customer.CustomerCity indeed maps to Customer.CustomerAddress.City.

2. Using Inheritance. I assume there is a main entity (PK side). So you could make the entityB inherits from entityA, then you will see entiityB at code as the total of fields of entityA and entityB. So you could rename enityB to become "TheWholeCustomerEntity".

Great!

Can you give me the steps/location in manual to do option 2, I couldn't figure that out.

• LLBLGenPro Help - Using the Designer - Inheritance mapping.
• http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=11614

Hope helpful

also an option is (if both tables have a 1-to-1 relation) is to create a view that contains all fields from both tables and then create an entity based on this view.