You need to sign in to do that
Don't have an account?
Pichala Palanikumar
Partial versus Full transaction
In one of the you tube video on sales force I saw that a transaction can be full or partial meaning fully rollback and partially completing the transaction.
In the case of full rollback it is database DML direct.
In the case of partial rollback it is via a page method.
Even without Salesforce this is true.
Under this situation instead of calling a stored procedure directly via execution at the backend only it either commits or roll backs.
If the same stored procedure is called from within a page then it is via page method. Here it is partial commit.
We experienced this recently.
However in order to solve this partial commit to full commit (either commit or rollback) at the page level can we implement holdlock on the calling stored procedure.
Will that work?
What other methods I can implement to prevent partial transaction?
Please advise.
In the case of full rollback it is database DML direct.
In the case of partial rollback it is via a page method.
Even without Salesforce this is true.
Under this situation instead of calling a stored procedure directly via execution at the backend only it either commits or roll backs.
If the same stored procedure is called from within a page then it is via page method. Here it is partial commit.
We experienced this recently.
However in order to solve this partial commit to full commit (either commit or rollback) at the page level can we implement holdlock on the calling stored procedure.
Will that work?
What other methods I can implement to prevent partial transaction?
Please advise.