Peter, First could you please respond to the individual meassages or if you do respond to the digest please change the subject in your reply to that of the message you are responding to in the digest. The digest is a summary of a day's posts and contains posts from multiple threads and we don't know which one you are responding to and the digest itself does not appear to get posted to the mail archive.
Not everyone uses Sqlite or even the DBMS backend. Many of us use the XML version with no problems, particularly for personal finances where it is low volume. On Linux (Mint 20.2) closing using Window close X (upper right) does invoke a dialog (which may be an OS feature and not necessarily programmed in the GnuCash code explicitly- not sure about that) which allows you to cancel the close dialog then save the data before closing. On LM File->Quit invokes a dialog prompting you to save data, as does using the Window X close, if there is any unsaved transaction data (Save button on toolbar not grayed out). Again not sure about other Linux distributions and or other OS. The lock file is always removed if I exit cleanly using the File->Quit procedure. The presence of the .LCK file can always be overridden on strtup if it is still present and you are sure there is not another instance of GnuCash which might have GnuCash open. I can open any of my data files from any of three computers on my LAN (and externally where a computer has been granted access to my Dropbox account where I store the data files). I personally don't rely on GnuCash automatically having saved data before exiting the program and forcible Save before exiting as a matter of habit after each data import or data entry session. I have only very occasionally lost a transaction or two (or a single import) when another program crashes the system while GnuCash has been running in the background. AFAIK the recommended procedure is to use the File->Quit menu entry to exit the program (File->Close from the menu closes open register tabs and not the program). David Cousens On Sun, 2022-01-23 at 10:28 +0800, Peter wrote: > I would like to thank all those who has responded to my initial email > about a possible error on exiting from gnucash while using XML > My next question has anybody been able to verify my observed problem? > As I said it is an interesting problem to me at least. As it happens I > have found the same issue in Linux(Ubantu). > > Last Friday I was talking to a colleague about this issue of how I found > a possible issue with the closing of gnucash while using XML. > We wondered if it would evolve into why are we using XML and not like > the rest of the world that use SQLite. How old fashion can we be? > > Unlike the vast majority of folks that have replied with it seems with > the possible exception John Layman - I make mistakes. > I also share John's thoughts on RDBMS and XML. For the size of my > database XML is just fine. > > I think the first course on RDBMS I did was some 30 years ago. Since > then my field experience with customers that ran RDBMS. > Some did snapshots others didn't Most of them had no idea how to restore > if they had a problem. I think I would still be correct. > This is like Apple approach to fixing a problem - bring out a new model > and dazzle everyone. Then the problem will go away. > > I don't really care if the issue is fixed, I really don't. It would seem > that there is this product called gnucash that has a problem if you use XML. > > My last question if this is known and everybody uses SQLite then why > don't change the documentation as to reflect the problem and then on > release 5 remove the support for XML? > As I said that's the Apple solution. > > Lastly I also think that the folks that are developing gnuscah do a > wonderful job and thank them whole heartedly. > > > On 23/01/2022 01:00, gnucash-user-requ...@gnucash.org wrote: > > Send gnucash-user mailing list submissions to > > gnucash-user@gnucash.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > or, via email, send a message with subject or body 'help' to > > gnucash-user-requ...@gnucash.org > > > > You can reach the person managing the list at > > gnucash-user-ow...@gnucash.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of gnucash-user digest..." > > > > Today's Topics: > > > > 1. Re: Exiting gnucash Lock file Vol 226, Issue 57 (John Layman) > > 2. Re: Split transaction (Liz) > > 3. Re: Split transaction (David Carlson) > > 4. Re: Split transaction (David Carlson) > > 5. Re: Split transaction (Michael or Penny Novack) > > > > _______________________________________________ > > > > gnucash-user mailing list > > gnucash-user@gnucash.org > > To update your subscription preferences or to unsubscribe: > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > If you are using Nabble or Gmane, please see > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > > ----- > > Please remember to CC this list on all your replies. > > You can do this by using Reply-To-List or Reply-All. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
