Command END TRANSACTION Foundation
Ends/commits a transaction and makes the changes permanent
BEGIN TRANSACTIONEnds the current transaction and saves any changes made to tables, memo and index files. All updates to the database that were made between the commands BEGIN TRANSACTION and END TRANSACTION are executed. If only one transaction is open the changes are written to disk. In a nested transaction only the updates cached for the next higher level transaction are executed by END TRANSACTION. This means that care must be taken to not overwrite the changes made at a higher level when nesting transactions.
If END TRANSACTION runs into an error, for example because there is insufficient disk space, the changes recorded in the transaction are discarded and the transaction is ended.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.