LastUpdated field on AggregateDigest is never used
Reported by Ben Hood | January 28th, 2011 @ 12:07 PM | in 0.9.3
The LastUpdated field was originally defined on the Digest super type before it was refactored to make a clear distinction between the AggregateDigest and EntityVersion, but it seems to have been unnecessarily maintained in AggregateDigest, although it is not used by the kernel at all.
Comments and changes to this ticket
-
Paul Jones February 3rd, 2011 @ 05:39 PM
- State changed from “new” to “open”
- Assigned user set to “Paul Jones”
-
Ben Hood February 3rd, 2011 @ 06:05 PM
(from [788d8ef3b51d84f0caf187276e9b7a36021a8ef8]) [#165] Remove lastUpdated from AggregateDigest. https://github.com/lshift/diffa/commit/788d8ef3b51d84f0caf187276e9b...
-
Paul Jones February 3rd, 2011 @ 06:05 PM
- State changed from “open” to “resolved”
- Assigned user changed from “Paul Jones” to “Ben Hood”
lastUpdated has been removed from the AggregateDigest (and Digest trait). It only exists on an EntityVersion now.
-
Ben Hood February 3rd, 2011 @ 08:01 PM
- no changes were found...
-
Ben Hood February 3rd, 2011 @ 08:04 PM
A note to people implementing queryAggregateDigests/2: this ticket will affect your Participant specifications.
-
-
-
Ben Hood February 4th, 2011 @ 02:48 PM
- Milestone set to “0.9.3”
- Milestone order changed from “11” to “0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
People watching this ticket
Ben Hood
Referenced by
-
165
LastUpdated field on AggregateDigest is never used
(from [788d8ef3b51d84f0caf187276e9b7a36021a8ef8])
[#165] ...
-
165
LastUpdated field on AggregateDigest is never used
(from [9dc155ef37f71461a19f778f1b43d9804f2f98b1])
Merged ...