Question

Our organization is looking to standardize on Entity Framework once v4 comes out. As a result, I am looking at what it would take to migrate our application that uses NHibernate for persistence to EF4 using POCO support. In a couple of places we use single table inheritance (also known as Table Per Hierarchy). I have been unable to get it to work using the following.

Payment (base class [should be abstract but having trouble there as well]) CreditCardPayment (concrete implementation) ACHPayment (concrete implementation) CheckPayment (concrete implementation)

Right now, I am mapping them with only the base class properties. All of these classes are in the same namespace. They have a discrimimator that is called PaymentTypeId in the database, so the Payment mapping has a condition of "When PaymentTypeId = 0". Each of the subclasses have the same condition with different values (i.e. CreditCardPayment = 1, etc.).

When I try to load each a list of all payments using DataContext.Payments.ToList() (DataContext inherits from ObjectContext) I am getting the following exception:

"Object mapping could not be found for Type with identity DataLayer.DataModel.CreditCardPayment ."

I can t figure out what this means, as the POCO CreditCardPayment class lives in the same namespace as the POCO Payment class does (in fact in the same file).

What am I missing?

Answer 1

What I didn t represent before (I didn t think it relevant, but it was). Was that CreditCardPayment inherited from an intermediary class named "CreditPayment" and ACHPayment inherited from CashPayment. CreditCardPayment and CashPayment live in the same namespace and file, but were not represented in the EF mapping. Once I added those within the mapping file, everything worked ok.

So, even thought EF does not ever map to one of those types directly, it seems to need to know about them, because it changes the basetype of the CreditCardPayment classes et al. Thank you for your help on this.

Answer 2

This is complaining not about database mapping, but model to CLR mapping.

The EF can t for some reason find your CreditCardPayment class.

Now one possible reason is that you haven t loaded the metadata for it yet.

For example if you have this:

Assembly 1:
 - Payment

Assembly 2 references Assembly 1:
 - CreditCardPayment extends Payment

Then when you query the EF doesn t know where CreditCardPayment lives.

The way to get around this is with LoadAssembly i.e:

using (DataContext ctx = new DataContext())
{
   ctx.MetadataWorkspace.LoadFromAssembly(typeof(CreditCardPayment).Assembly);

   // now do your query.

}

You need to tell to LoadFromAssembly every assembly that isn t directly reference by your DataContext class.

Note: typeof(Payment).Assembly is directly referenced because of the IQueryable<Payment> Payments property.

Hope this helps

Alex

Microsoft.

友情链接