On 3/7/19 7:22 AM, David G Hamblen wrote: > In the past, I've had problems with a mysql file, just getting > seqfaults. Turned out that I was entering a transaction with a 1962 > date. I forget the details, but mysql stored it as a zero, which I > couldn't reopen. I changed the date (to post-1970?) with the mysql > command line tool. Perhaps more recent versions of GC handle this better. >
In the old days, and perhaps to this day, UNIX and Linux systems had no dates prior to 1970/01/01. Maybe mysql still has this limitation. In the early days of UNIX, it ran on 16-bit machines and they kept time to the second in a double-precision format. Now, with 64-bit machines being de rigueur, time is kept more accurately, and will not run out in 2038. ;-) -- .~. Jean-David Beyer /V\ PGP-Key:166D840A 0C610C8B /( )\ Shrewsbury, New Jersey ^^-^^ 10:20:01 up 4 days, 19:23, 2 users, load average: 5.19, 5.19, 4.99 _______________________________________________ gnucash-user mailing list [email protected] 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.
