Re: [GNC] GnuCash Bug report 798798

2023-03-24 Thread jralls


Stan,

Please don't write directly to anyone on the GnuCash team unless expressly 
asked to. Always use the mailing lists or IRC.

You sort of went to the wrong place, but it's not really your fault. The link 
that you followed is to open a new *GnuCash* bug, but you wanted to open a 
*Documentation* bug. The direct link for that is 
https://bugs.gnucash.org/enter_bug.cgi?product=Documentation . It's not on the 
wiki page, but I'll fix that.

Regards,
John Ralls

> On Mar 24, 2023, at 2:43 PM, Stan Brown  wrote:
> 
> Thanks, John.
> 
> I would have used "Documentation" if it had been an option in the bug
> reporter. Did I go to the wrong place?
> 
> I started at  then followed "Q: I
> think I found a bug. How do I report it?" to
> . From there I searched the bug
> database as described under "Triage". Not finding my issue already
> reported, I continued to "Commenting on existing bugs or entering new
> ones" and to "Open a new GnuCash bug", at
> .
> "Documentation" was not listed among the Components, so following the
> instructions at 
> I selected "General".
> 
> -- 
> Stan Brown
> Tehachapi, CA, USA
> https://BrownMath.com

___
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.


Re: [GNC] Gnucash bug

2019-07-30 Thread Mike or Penny Novack

On 7/30/2019 3:52 AM, Wm via gnucash-user wrote:

On 09/07/2019 03:45, John Ralls wrote:



On 8 juil. 2019, at 08:55, R. Victor Klassen  
wrote:


Perhaps this has been fixed. I’m using 2.6.21 for production.

Using SQLite I am expecting every transaction to hit disk immediately.

Saturday we had a power failure and lost about five days’ worth of 
transactions including at least 10 invoices and three new customers.


I think I can reconstruct. But I wouldn’t expect this to have happened.
 It is also a "work flow" issue. You SHOULD want "clean" recovery 
points. So what you should ask yourself is whether you should make sure 
of an EXPLICIT save:

1) After entering transactions for a day
2) After entering data like "customers"

Do you understand what I am saying? Even if SQLite were saving data 
after each entry (I am used to SQL systems that would need a "commit") 
you would not know WHERE you were at.


Michael D 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.


Re: [GNC] Gnucash bug

2019-07-30 Thread Wm via gnucash-user

On 09/07/2019 03:45, John Ralls wrote:




On 8 juil. 2019, at 08:55, R. Victor Klassen  wrote:

Perhaps this has been fixed. I’m using 2.6.21 for production.

Using SQLite I am expecting every transaction to hit disk immediately.

Saturday we had a power failure and lost about five days’ worth of transactions 
including at least 10 invoices and three new customers.

I think I can reconstruct. But I wouldn’t expect this to have happened.


Were those 5 days worth of transactions all entered together or over the 5 days? Do the 
transaction logs reflect the "lost" transactions? If so you can at least 
recover them by playing the transactions back
https://www.sqlite.org/howtocorrupt.html might shed some insight on what 
happened.


I think
===
I’m using 2.6.21 for production.
===
is more likely to be the problem.

--
Wm

___
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.


Re: [GNC] Gnucash bug

2019-07-08 Thread John Ralls


> On 8 juil. 2019, at 08:55, R. Victor Klassen  wrote:
> 
> Perhaps this has been fixed. I’m using 2.6.21 for production. 
> 
> Using SQLite I am expecting every transaction to hit disk immediately. 
> 
> Saturday we had a power failure and lost about five days’ worth of 
> transactions including at least 10 invoices and three new customers.   
> 
> I think I can reconstruct. But I wouldn’t expect this to have happened. 

Were those 5 days worth of transactions all entered together or over the 5 
days? Do the transaction logs reflect the "lost" transactions? If so you can at 
least recover them by playing the transactions back
https://www.sqlite.org/howtocorrupt.html might shed some insight on what 
happened. 

Regards,
John Ralls

___
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.


Re: [GNC] Gnucash bug

2019-07-08 Thread R. Victor Klassen
Local file.  Not a backup.  Accessing a backup would be an XML issue.

> On Jul 8, 2019, at 3:48 PM, Adrien Monteleone 
>  wrote:
> 
> Is your data file local or on a network? If a network, there might be 
> something that has interfered with the data being written. Also, be certain 
> you’re accessing the current file and not a 5 day old backup. (usually the 
> case in threads where users find data ‘missing’)
> 
> Regards,
> Adrien
> 
>> On Jul 8, 2019, at 10:55 AM, R. Victor Klassen  wrote:
>> 
>> Perhaps this has been fixed. I’m using 2.6.21 for production. 
>> 
>> Using SQLite I am expecting every transaction to hit disk immediately. 
>> 
>> Saturday we had a power failure and lost about five days’ worth of 
>> transactions including at least 10 invoices and three new customers.   
>> 
>> I think I can reconstruct. But I wouldn’t expect this to have happened. 
>> 
> 
> 
> ___
> 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.


Re: [GNC] Gnucash bug

2019-07-08 Thread Adrien Monteleone
Is your data file local or on a network? If a network, there might be something 
that has interfered with the data being written. Also, be certain you’re 
accessing the current file and not a 5 day old backup. (usually the case in 
threads where users find data ‘missing’)

Regards,
Adrien

> On Jul 8, 2019, at 10:55 AM, R. Victor Klassen  wrote:
> 
> Perhaps this has been fixed. I’m using 2.6.21 for production. 
> 
> Using SQLite I am expecting every transaction to hit disk immediately. 
> 
> Saturday we had a power failure and lost about five days’ worth of 
> transactions including at least 10 invoices and three new customers.   
> 
> I think I can reconstruct. But I wouldn’t expect this to have happened. 
> 


___
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.


[GNC] Gnucash bug

2019-07-08 Thread R. Victor Klassen
Perhaps this has been fixed. I’m using 2.6.21 for production. 

Using SQLite I am expecting every transaction to hit disk immediately. 

Saturday we had a power failure and lost about five days’ worth of transactions 
including at least 10 invoices and three new customers.   

I think I can reconstruct. But I wouldn’t expect this to have happened. 

Sent from my iPhone
___
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.