Autosaving stacks corrupted on network drives

[Mike Kerner]

Yes.  Transactions are the individual operations, i.e. an audit trail.
Then if there is corruption in the db, it is able to "play back" the
transactions to recreate it.

On Wed, Oct 25, 2017 at 10:31 AM, tbodine via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Thanks, Mark and Trevor, for those ideas.
>
> >>Mark wrote:
> Split the data out into a separate data file or better into a database
> (because most databases use transactions, with greatly minimizes the
> probability of corruption).
>
> Does "databases use transactions" mean DBs don't rewrite the entire file
> when there is a Save operation, but only write the changes into the DB
> file?
> (Hence, faster saves?)
>
> Tom B.
>
>
>
>
> --
> Sent from: http://runtime-revolution.278305.n4.nabble.com/
> Revolution-User-f278306.html
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."