epriestley f46263903c Fix improper filtering behavior in ConpherenceParticipantQuery ... Summary: Pathway to D17685. This fixes an issue idenified in D17731: if any caller ever queried for more than one participant, some results could get thrown away by re-keying the results on thread PHID: two different participants can be members of the same thread! This also fixes an issue from D17683, where a `needParticipantCache()` callsite was overlooked. Test Plan: - Viewed Conpherence dropdown. - Sent messages, saw unread count / thread order still work properly. Reviewers: chad Reviewed By: chad Differential Revision: https://secure.phabricator.com/D17732		2017-04-19 13:59:47 -07:00
..
ConpherenceFulltextQuery.php	Update Phabricator to use intermediate tokens from the query compiler	2017-04-12 19:07:33 -07:00
ConpherenceParticipantCountQuery.php	Remove "participationStatus" from ConpherenceParticipant	2017-04-19 13:58:42 -07:00
ConpherenceParticipantQuery.php	Fix improper filtering behavior in ConpherenceParticipantQuery	2017-04-19 13:59:47 -07:00
ConpherenceThreadQuery.php	Remove recentParticipants from ConpherenceThread	2017-04-13 13:55:08 -07:00
ConpherenceThreadSearchEngine.php	Remove recentParticipants from ConpherenceThread	2017-04-13 13:55:08 -07:00
ConpherenceTransactionQuery.php	Fix Conpherence transaction ordering	2015-04-13 12:34:37 -07:00