This question is locked. New answers and comments are not allowed.
Hello,
I have a webapplication and a data application with a model.
I see the following happening: I open a entity at page load of Page1.aspx and save the entity to the session. on postback I change a property of the entity. Then, without saving anything, the user skips to Page2.aspx, that has nothing to do with Page1.
Now, the changes are save to the database... why? I did not do any save actions.
I've been reading about transactions, but only see a autostart. Also I see concurrency possibilities, but what exactly influences the above behaviour I cannot say. I find the doc somewhat poor/short (still, pointed this out a few times now) and w/o any example, not even an elaboration/textual example to put it in context...
So, why does the OA context autocommit when there was no data saved explicitly? How can I change this behaviour to explicit saving?
Erik
I have a webapplication and a data application with a model.
I see the following happening: I open a entity at page load of Page1.aspx and save the entity to the session. on postback I change a property of the entity. Then, without saving anything, the user skips to Page2.aspx, that has nothing to do with Page1.
Now, the changes are save to the database... why? I did not do any save actions.
I've been reading about transactions, but only see a autostart. Also I see concurrency possibilities, but what exactly influences the above behaviour I cannot say. I find the doc somewhat poor/short (still, pointed this out a few times now) and w/o any example, not even an elaboration/textual example to put it in context...
So, why does the OA context autocommit when there was no data saved explicitly? How can I change this behaviour to explicit saving?
Erik