Abstract: Techniques for handling data access conflicts are disclosed. In some embodiments, a conflict handling system detects a set of one or more objects that are currently being accessed by an application. The conflict handling system queries a database to determine whether the set of one or more objects have changes pending. Responsive to determining that an object has a change pending, the conflict handling system identifies and loads, at runtime of the application, a set of one or more application-specific rules that are defined for handling data conflicts. The conflict handling system executes the rules to generate a conflict resolution result for the object. The application may then perform an application-specific function based on the conflict resolution result.

Abstract: Techniques are described handling database transaction in a manner that is efficient and flexible. In some embodiments, a system receives, through a page of a user interface, a first request to change at least a first data object. The system generates, based on the first request, a first atomic transaction to modify the first data object in a database. Before the first atomic database transaction has committed to the database, the system receives, through the page of the user interface, a second request to change at least a second data object. The system generates, based on the second request, a second atomic transaction to modify the second object in the database. The system may execute the second atomic transaction independently of the first atomic transaction.

Abstract: Techniques for handling data access conflicts are disclosed. In some embodiments, a conflict handling system detects a set of one or more objects that are currently being accessed by an application. The conflict handling system queries a database to determine whether the set of one or more objects have changes pending. Responsive to determining that an object has a change pending, the conflict handling system identifies and loads, at runtime of the application, a set of one or more application-specific rules that are defined for handling data conflicts. The conflict handling system executes the rules to generate a conflict resolution result for the object. The application may then perform an application-specific function based on the conflict resolution result.

Abstract: Techniques are described herein for handling transactions where only a portion of submitted changes are committed. In some embodiments, a system receives, through a page of a user interface, a request to submit a plurality of changes to a set of data objects. The system identifies, based on the page of the user interface through which the request was submitted, a first subset of one or more changes that require further review and a second subset of one or more changes that do not require further review before being committed to the database. The first subset of one or more changes are cached for further review, and a respective approval transaction may be initiated. A commit transaction may be initiated directly for the second set of one or more changes to commit the changes to the database without further review.

Abstract: Techniques are described handling database transaction in a manner that is efficient and flexible. In some embodiments, a system receives, through a page of a user interface, a first request to change at least a first data object. The system generates, based on the first request, a first atomic transaction to modify the first data object in a database. Before the first atomic database transaction has committed to the database, the system receives, through the page of the user interface, a second request to change at least a second data object. The system generates, based on the second request, a second atomic transaction to modify the second object in the database. The system may execute the second atomic transaction independently of the first atomic transaction.

Abstract: Techniques are described herein for handling transactions where only a portion of submitted changes are committed. In some embodiments, a system receives, through a page of a user interface, a request to submit a plurality of changes to a set of data objects. The system identifies, based on the page of the user interface through which the request was submitted, a first subset of one or more changes that require further review and a second subset of one or more changes that do not require further review before being committed to the database. The first subset of one or more changes are cached for further review, and a respective approval transaction may be initiated. A commit transaction may be initiated directly for the second set of one or more changes to commit the changes to the database without further review.

Abstract: Techniques for handling data access conflicts are disclosed. In some embodiments, a conflict handling system detects a set of one or more objects that are currently being accessed by an application. The conflict handling system queries a database to determine whether the set of one or more objects have changes pending. Responsive to determining that an object has a change pending, the conflict handling system identifies and loads, at runtime of the application, a set of one or more application-specific rules that are defined for handling data conflicts. The conflict handling system executes the rules to generate a conflict resolution result for the object. The application may then perform an application-specific function based on the conflict resolution result.