Feedback about 2.7.8
wm_o_o_o at yahoo.co.uk
Sun Apr 1 13:11:29 EDT 2018
On 28/03/2018 20:20, Christoph R wrote:
> Hi Geert,
>> Am 28.03.2018 um 17:24 schrieb Geert Janssens <geert.gnucash at kobaltwit.be>:
>> Op woensdag 28 maart 2018 15:46:26 CEST schreef Christoph R:
>>> It choked on one of my files, which worked fine with 2.6 and was probably
>>> created with 2.4 or even earlier. There was an out-of range date in the
>>> price database which I corrected manually. But normal users would have been
Just for general info (and I know you probably know), a wild price like
this in the price db is unlikely to have any actual effect on accounting
as the price db is just that, a db of prices at a time and no sensible
person is going to value their assets significantly out of time. The
question is how much should we check for mistakes, if we do that too
much we never get anything done.
Do you feel this was an anomaly or a general case that needs to be coded
for ? Maybe we should just drop prices far in the past or future ? The
price db really isn't that important, it doesn't contain anything real
for a person's actual accounts as I very much doubt anyone using gnc
gets wholesale market prices on stocks or currencies, etc.
>> What was the date set to before you corrected it ? And how does it display in
>> gnucash 2.6 if you look at that particular price in the Price editor ?
> Date was <ts:date>1301-09-13 00:05:08 +0053</ts:date>
> and it shows up absolutely correct as 13.9.1301 :-)
You're older than I thought :)
Have you had your data in and out of a mysql db ? I think there was a
date thing there (almost no one use postgres and sqlite would have been
noticed by too many).
More information about the gnucash-devel