ed. If 
object is updated multiple times during transaction, shadow is create only once. 
Because of using shadows, DyBASE does not need a transaction log file. So in DyBASE
long transaction can not cause transaction log overflow as in most of other DBMSes.
Quite the contrary, if you do not call commit at all, DyBASE works as DBMS without transaction
support, adding almost no overhead of supporting transactions.<P>

The only drawback of long transactions is possibility to loose a lot of changes in case of f