4D v14.3In transaction |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
4D v14.3
In transaction
In transaction
The In transaction command returns TRUE if the current process is in a transaction, otherwise it returns FALSE. If you perform a multi-record operation (adding, modifying, or deleting records), you may encounter locked records. In this case, if you have to maintain data integrity, you must be in transaction so you can “roll-back” the whole operation and leave the database untouched. If you perform the operation from within a trigger or from a subroutine (that can be called while in transaction or not), you can use In transaction to check whether or not the current process method or the caller method started a transaction. If a transaction was not started, you do not even start the operation, because you already know that you will not be able to roll it back if it fails. |
PROPERTIES
Product: 4D
HISTORY
Created: 4D v6 SEE ALSO
CANCEL TRANSACTION ARTICLE USAGE
4D Language Reference ( 4D v11 SQL Release 6) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||