Activity log for bug #313125

Date Who What changed Old value New value Message
2009-01-02 05:32:52 Joshua Cronemeyer bug added bug
2009-01-02 05:46:36 Joshua Cronemeyer shellsink: importance Undecided High
2009-01-02 05:46:36 Joshua Cronemeyer shellsink: statusexplanation
2009-02-08 15:56:41 Joshua Cronemeyer shellsink: status New Confirmed
2009-03-08 16:58:49 Joshua Cronemeyer shellsink: importance High Wishlist
2009-03-08 16:58:49 Joshua Cronemeyer shellsink: assignee joshuacronemeyer
2009-03-08 16:58:49 Joshua Cronemeyer shellsink: statusexplanation Move to wishlist. I looked into this and it seems more trouble than it is worth. The problem is that the atom feed is created by querying the commandTags but the annotations are put directly on the commands. So changing the timestamp on the command has no effect on the sorting of the commandTags. Whatever the solution it would have to take into account that things displayed in the RSS are filtered by tag, so you couldn't just sort the latest annotations. Basically I can't think of a good implementation path. With the current implementation you would have to update every commandTag for the command that you had annotated. That would involve a query for every tag in the system, which is crap... could be done on the client with ajax, but still crap. if you have a large number of tags this becomes too expensive. The only thing I thought of that would sort of make this work would be a separate rss feed for annotations and maybe an option for mixing your regular feed with the annotation feed. not too good since it means you would have to be careful not to annotate commands you wanted to keep private. Anyway, unless somebody can suggest a good way to do this that scales well in big table I'm probably not going to.