1

I have a GridView bound to an EntityDataSource. Automatic Updates/Inserts/Deletes are enabled, and these operations function correctly.

However, I'd like to make multiple edits before commiting anything to the database. (vs. committing each row as soon as the Update button is clicked.) When the user finally clicks a Save button, all the page's edits shall be committed. e.g. myEntityModel.SaveChanges();

This link says to copy the data to a new table and bind the GridView to that. Would that be the recommended approach for Entity Framework (4.0), or is there a better way?

Thanks!

Community
  • 1
  • 1
Mark Maslar
  • 1,121
  • 4
  • 16
  • 28

1 Answers1

0

Yes, its right way to do that. look here for some interesting discussion on this topic. I mean calling savechanges at last, till that time modified entities will be persisted virtually.

note: Batch update is not currently done by EF, even you say save changes multiple queries will hit to database. There are other way around to achieve this.

Community
  • 1
  • 1
indiPy
  • 7,844
  • 3
  • 28
  • 39
  • 1
    seems not but there is place where you can vote http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions and this extension http://weblogs.asp.net/pwelter34/archive/2011/11/29/entity-framework-batch-update-and-future-queries.aspx support batch updates but not inserts. – indiPy Nov 21 '12 at 10:03