DBtransactionEnd |
Top Previous Next |
Changes in log file write. Moskito puts in to every Workfile *.wf a transaction log *.tr. In this file all changes in the Workfile are carried along. As soon as a transaction is finished, the log file is physically written. After successful securing of the Workfiles at the end of a Moskito's meeting the log file is removed. If Moskito hits by the start on an available log file, Moskito has broken off before. And the Workfileinhalt is reconstructed with the help of the last valid transaction. Every transaction can be cancelled about access functions and be restored. A transaction is concluded with this function in the log file. Taking the minutes happens as follows: First a new entry is generated with DBtransactionStart in the log file. Then there follow one or several functions which change the contents of the data bank. The changes in the data bank have to go with the routine DBtransactionData are taken down. In the end DBtransactionEnd which writes the change protocol in the log file is called. Parametre root (PROOT) [IN] Act on the open data bank. Result (long int) [OUT] If exists no log file the size of the written changes becomes 0 zurückgeliefert, otherwise in the log file. Declaration #include "database.h"
long int DLLENTRY DBtransactionEnd ( PROOT root ); Related functions DBtransactionSetUndoImpossible
|