sunfish62 at yahoo.com
Thu Jul 17 15:09:23 EDT 2008
I've read most but not all of the many messages in the two threads on this topic. It is clear that there is a lot of passion around the issue.
>From my (end-user) perspective, I agree with (I think) Graham that the transaction date that displays in the register should be a date-only entry. I say this because from my perspective, I have transactions with a date only; I write my checks with a date only, and my bank statement has date-only. So this entry should be date-only. This date would be set once and would not fluctuate with the machine's timezone.
I think, however, a universal timestamp value is critical for recordkeeping purposes within the accounting system (i.e., Gnucash itself). Such a timestamp could presumably also serve the purpose of sorting transactions in the register. As an absolute in time value, it would change as the machine's timezone changed.
It seems to me that separating the different functions of this datum into different spots might help the system perform more reliably.
More information about the gnucash-devel