Ticket #131 (new defect)

Opened 3 years ago

Last modified 3 years ago

Remove event adoption and replace owner with last person who modified event

Reported by: obaltzer Assigned to: somebody
Priority: high Milestone: 0.8.0
Component: General Version: HEAD
Severity: normal Keywords: cleanup
Cc:

Description

Since Rails does not include a DISTINCT operator into the query it will retrieve very long results when an event has changed its owner a few times and will make the events unique internally. This is very inefficient and requires a rethinking about events ownership.

Change History

04/09/05 11:28:18 AM changed by obaltzer

  • severity changed from normal to Non-Critical Bug.
  • branch set to trunk.

04/09/05 11:28:41 AM changed by obaltzer

  • priority changed from highest to high.

04/09/05 11:44:11 AM changed by obaltzer

  • version set to 1.0-final.

04/09/05 11:53:34 AM changed by obaltzer

  • milestone deleted.

04/09/05 11:57:26 AM changed by obaltzer

  • version changed from 1.0-final to 1.00.

12/09/05 09:11:23 PM changed by obaltzer

  • version changed from 1.00 to HEAD.

14/09/05 12:09:40 AM changed by cjordan

I realize that this may not be a good solution but it is one. We can make an association between users and events with the activities as the join table. The association would be return the list of users that have editted the event in some form. We can then order this list in descending order by time. The first user in this list would be the owner.

01/10/05 12:31:34 PM changed by obaltzer

  • summary changed from (Events Ownership Problem) Ticket adoptions leads to long query results to (Events Ownership Problem) Event adoptions leads to long query results.

01/10/05 12:37:02 PM changed by obaltzer

  • keywords set to cleanup.
  • summary changed from (Events Ownership Problem) Event adoptions leads to long query results to Remove event adoption and replace owner with last person who modified event.
  • milestone set to 0.6.0.

The last user that modifies an event is held accountable for the event and thus becomes the owner of the event. Just query on event_id and updated_on in the acitivies table.