It has a DefiningQuery but no InsertFunction element... err2009-10-19 asp.net entity-framework
This thing is driving me crazy, and the error is quite meaningless to me:
Unable to update the EntitySet 'TableB' because it has a DefiningQuery and no element exists in the element to support the current operation.
My tables are put like this:
TableA int idA (identity, primary key) ... TableB int idA (FK for TableA.idA) int val
TableB has no defined primary key in the SQL server. The Entity Framework has imported the table and the association and set both fields as key. But it will output that error when I try to do an insert into the table!
Edit: As suggested by Alex, the solution was this:
- Right click on the edmx file, select Open with, XML editor
- Locate the entity in the edmx:StorageModels element
- Remove the DefiningQuery entirely
- Rename the store:Schema="dbo" to Schema="dbo" (otherwise, the code will generate an error saying the name is invalid)
- Remove the store:Name property
I left the key as it was, since it was OK to me that both the columns are part of the key.
Well when a table is encountered without a PrimaryKey it is treated as a View.
And views show up in the EDMX file (open in an XML editor to see) in the StorageModel\EntitySet[n]\DefiningQuery element.
When you have a DefiningQuery the Entity becomes readonly unless you add modification functions. You need 3 modifications functions (aka Stored Procedures) one for each of Insert, Update and Delete.
But you have two options:
Change the key definion:
- And convince the EF that what it thinks is a view is really a table
- Or add the appropriate modification functions
In your case I recommend (1).
@Palantir. Verify that both of you tables have Primary Keys set, and be careful with multiple primary keys set in a table.
Just Add a primary key to the table. That's it. Problem solved.
ALTER TABLE <TABLE_NAME> ADD CONSTRAINT <CONSTRAINT_NAME> PRIMARY KEY(<COLUMN_NAME>)
I was missing a primary key on my table and got this error message. One thing I noted was after I added the key to the table, I needed to clear the table from the edmx using the designer, save the edmx, then update it again to add the table back in. It wasn't picking up the key since it was already assigned as a view. This didn't require editing the edmx manually.
Add primary key to table, delete the model from the edmx model, then select update from database, build and run...... works
- You need to manually open the .EDMX file in notepad or notepad++ or in any text editor of your choice.
- Locate the entry in edmx:StorageModels in file opened in step1.
- Find the DefiningQuery element and remove this tag entirely.
- Find the store:Schema="dbo" to Schema="dbo" (if you skip this step it will generate error of the name is invalid).
- Save and close the file.
Hope it will solve the problem.
- Unable to update the EntitySet - because it has a DefiningQuery and no <UpdateFunction> element exist
- Why does Entity Framework (EF 6.0) generate a view and not a table for linking tables which causes inserts to fail?
- Entity not being saved, DbUpdateException was unhandled
- Entity Framework 6 Code First, Composite Foreign Key
- In Entity framework load child in parent entity (non primary key association)
- Unable to update entityset because it has a definingquery and no element exists in the element to support the current operation
- EF Error - Unable to update the EntitySet because it has a DefiningQuery
- entity framework 4.0 with STEs: how to delete a many to may relationship without delete registers