On Mon, 17 Aug 2009 10:05:52 -0400, Derek Atkins <warl...@mit.edu> wrote: > Marcus, > > Marcus Wolschon <mar...@wolschon.biz> writes: > >> There must be a way without violating 1st normal form and storing >> everything twice. >> Maybe an "updated"-timstamp or something may help. > > Maybe... I was thinking about ways to avoid using timestamps per se, > because the current time can vary machine-to-machine.
I'm not sure my mail made it to the list, so here again: Timestamps are created with the "now()" SQL-function and are ALWAYS server-time. Never create a timestamp on a client. That would be bad practice. Marcus _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
