I believe the prev filtering in the SQL clause is supposed to only show the latest activity per conversation. However, it currently filters independent of matching memberId, which I think is a bug. Why should a later activity intended for another member hide activities of the current user? For me, this causes the notification view in the forum to magically miss notifications I would expect there, simply because a later activity has been registered for a different user.
I believe the
prevfiltering in the SQL clause is supposed to only show the latest activity per conversation. However, it currently filters independent of matchingmemberId, which I think is a bug. Why should a later activity intended for another member hide activities of the current user? For me, this causes the notification view in the forum to magically miss notifications I would expect there, simply because a later activity has been registered for a different user.