postponing changes to the database while using gridview-sqldatasoruce

[Aamir Ghanchi]

http://groups.google.com/group/microsoft.public.dotnet.framework.aspnet/msg/01cdac5093057079

Hi, above is the link to a question posted by soomeone in this
usergroup an year ago, but it never got answered. I have exactly the
same question.
Is their a way for a (non paged) gridview-sqldatasource duo to hold
off any changes to the actual database till the user clicks a save
button (outside of the gridview). I would love to use the edit/delete
functionality gridview provides, but not to make the changes right
away to the database when the user clicks the Update or Delete
linkbuttons in the EditItemTemplate. Any response will be appreciated.
thanks!

 

[bruce barker]

trival, as this is builtin.

use a dataset (stored in session) to bind the gridview to. then on save,
apply the dataset changes. extra points for using a typed dataset.

-- bruce (sqlwork.com)

 

[Aamir Ghanchi]

trival, as this is builtin.

use a dataset (stored in session) to bind the gridview to. then on save,
apply the dataset changes. extra points for using a typed dataset.

-- bruce (sqlwork.com)






- Show quoted text -

Bruce, thanks for the response.

This means that I have to do away with the sqldatasource then. oh
well.
thanks again!