Commit related to AdvancedTable

Question

Hi,
I have a create page, which is based on AdvancedTable region. It allows user to enter new rows on click of "Add Another Rw" button.
It has a create button in pageButton bar region.
It has a delete option as a column in table, so that individual records can be deleted.
Now the scenario is:
The user creates two records in table (create button not clicked as yet) and decides to delete the first record. The delete method has a commit in it due to which the 2nd record gets inserted in database.
The user now clicks on cancel button instead of create button. This means that there should be no record in database. But since commit was performed during delete event, the 2nd record has already been inserted which should not be the case.
To handle this, when the user clicks on cancel button, a check on vo is done for records. If record exists i delete them.
Can this be handled in some more appropriate way....?
Thanks & Regards,
Mitiksha

Answer 1

you should not commit each DML transaction, instead you should just issue one commit when the user saves the data in the page, after doing any DML sequence, of create/update/delete.
When the user is done with the changes, and saves the data in the page, commit the transaction, if he cancels and moves out of the page, you do not issue a commit and all user interactions on the page is reverted back (from the UI, as the DB is not yet affected).
Thanks
Tapash