Hmm, I suppose another approach and possible horrible hack might be:
1. Create a queue of updates to the Content object
2. Votes are appended to the queue and immediately added to the
UserContentRelationship table.
3. A separate thread processes the queue periodically to ensure atomic
updates to
Yes, this is yet another voting design discussion.
As far as I can see there are two approaches:
1. A separate table that records the User-Content relationship
including the vote -1/0/+1
and, optionally:
2. A voting field in with the content that gets atomically updated
with each vote.
Just g
2 matches
Mail list logo
