Save One Row Per Transaction property
Use the Save One Row Per Transaction property to specify whether to save each modified row in a separate transaction. The property applies to primary and secondary collections.
| Setting | Description |
|---|---|
| True | Each modified row is saved in a separate transaction. When the user executes a save operation on the collection, the user client sends all modified rows to the middle tier to be processed. The middle tier then executes a save-current operation for each row. If the save succeeds, the next row is processed. If it fails, processing stops and an error message is presented; the previous rows remain committed. |
| False | Default. All modified rows are sent to the middle tier to be processed within a single transaction, which is rolled back if there is a failure. |
Caution:
If your form design requires that all modified rows be committed as a
unit, with processing on the unit before and/or after a save operation,
saving rows in separate transactions may not be appropriate. If an error
occurs on a row, some rows may be committed and others not committed.
Saving one row per transaction can alleviate blocking problems in some forms. Whether the setting enhances performance depends on the complexity of a form's save operation and the speed of your network connection. Forms that require highly complex saves may benefit from the setting, especially if connection speed is adequate. Forms that require simple save operations are less likely to benefit, especially if the additional network traffic required in saving one row at a time slows the system.