Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #81 (closed)

Opened 14 years ago

Closed 14 years ago

Implement update Event functionality.

Reported by: jamoore Owned by: jamoore
Priority: major Milestone: 3.0-M3
Component: Model Keywords: iteration5
Cc: jrswedlow Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.


Currently only the creation Events are being linked from each entity. Update Events are recorded but not on each row.

Change History (7)

comment:1 Changed 14 years ago by jmoore

  • Component changed from API to Model
  • Summary changed from Implement updateEvent functionality. to Implement update Event functionality.

comment:2 Changed 14 years ago by jmoore

  • Milestone changed from 3.0-M2 to 3.0-M3

This is important and tied to the security system (#114) . Will rev up in milestone:3.0-M2

comment:3 Changed 14 years ago by jmoore

  • Cc jason added
  • Keywords iteration5 added

Discussion during ConfCall Sep. 7, 2006 decided to only store last modification.

comment:4 Changed 14 years ago by jmoore

r962 implements the update event logic:

  • finally sets updateEvent to not null
  • adds 0 update_id to data.vm and common/build.xml
  • added setUpdateEvent() call in CurrentDetails (transient)
  • added a "pre-update" event listener to ~asynch. update the update event (managed)
  • added security checks in BasicSecuritySystem
  • misc: refactored more methods out to HibernateUtils

The semantics are such that no one can manually alter the update event of an entity, but if the entity is updated (or locked) that it's update event will be automagically incremented to the current event.

comment:5 Changed 14 years ago by jmoore

r962 caused #366, leaving in place because the update functionality is more important.

comment:6 Changed 14 years ago by jmoore

Note: automagically incrementing the update event is similar to updating the version. In fact, as long as versions are broken (#118) this may indeed help us catch many of the spurious deletes.

Could it completely replace versioning?

comment:7 Changed 14 years ago by jmoore

  • Resolution set to fixed
  • Status changed from new to closed

See #118 for all further discussion on versions v. updateEvent. Closing.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.290799 sec.)

We're Hiring!