[EMAIL PROTECTED] (Linas Vepstas) writes:
> On Fri, Apr 09, 2004 at 02:12:54PM -0400, Derek Atkins was heard to remark:
>> Neil Williams <[EMAIL PROTECTED]> writes:
>>
>> If the GUID matches it's the always same semantic object, regardless
>> of whether other data fields are changed.
>
> I having been toying with the idea of always adding a version
> number as a mandatory part of all objects, so that if you have
> two objects with the same guid, then you know which one is the more
> recent one.
I've been leaning towards a UTC timestamp instead of a version number.
Should do the same thing effectively, but lets you make multiple
changes without increasing the "version number" multiple times. I
also think the backend should control the timestamp, not the
engine/cache. The version/timestamp can be "modified" in the cache
during the commit_edit() phase.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
