Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Want how the Commit work statement behaves.

Former Member
0 Likes
530

Want how the Commit work statement behaves.

Like if 2 programs are updating the same table and they have read the same record and are trying to update the same . One is using commit work immediately and the other is using commit work afterwards. Which of these changes will get reflected.

These are 2 different programs.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
502

Hello ,

Obviously the fist commit will update the table.

But here they might be updating the values in the table as it is a same record. Insertion is not possible as it will leads to dump.

1. Commit work :

Commit work performs a database commits and closes the Logical unit of work in a asynchronous way.

2. Commit work cannot be used in call function update task.

3. a commit work can use for calling performs also.

Thanks,

Krishnakumar

3 REPLIES 3
Read only

Former Member
0 Likes
503

Hello ,

Obviously the fist commit will update the table.

But here they might be updating the values in the table as it is a same record. Insertion is not possible as it will leads to dump.

1. Commit work :

Commit work performs a database commits and closes the Logical unit of work in a asynchronous way.

2. Commit work cannot be used in call function update task.

3. a commit work can use for calling performs also.

Thanks,

Krishnakumar

Read only

Former Member
0 Likes
502

they will be sequently, but they don´t allowed to insert the same record, if you want to solution this problem, you can use the "que" and "deque" functions.

regards

Read only

Former Member
0 Likes
502