Hi Jim,
> Beware of confusion: the word "transaction" is already used on this list
> to mean an "accounting record of an exchange of value". But I suspect
> that here you use the word "transaction" to mean a "controlled and
> reliable change to data stored in a database".
Yes. They are similar. Both represent "atomic" updates, meaning "all or
nothing".
>> * Are transactions implemented? -- Let's assume, "Yes."
Let's assume, "No." (-: Apparently SQLite represent zero improvement over the
flat file storage.
Is there a way to update backing store anytime I make a change, and not
periodically? It seems like leaving updates lying around in memory is a good
way to lose updates when the dog pulls the plug out of the wall.
Thanks for the help,
--
Chris.
V:916.799.9461
F:916.974.0428
A: Because we read from top to bottom, left to right.
Q: > Why should I start my reply below the quoted text?
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
