MySQL sync

marcus.wolschon at marcus.wolschon at
Tue Aug 18 04:43:58 EDT 2009

On Mon, 17 Aug 2009 10:05:52 -0400, Derek Atkins <warlord at MIT.EDU> wrote:
> Marcus,
> Marcus Wolschon <Marcus at> 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.


More information about the gnucash-devel mailing list