Table architecture for relevancy scores
Hello,
I have a postVotes table linking users to posts. Currently using table aggregates to efficiently count total votes per post for display.
Now I need to implement post relevancy scoring (combining vote count + time decay), but this requires accessing vote data that's abstracted behind the aggregate layer, so I can't compute relevancy without n+1 querying each time, or going through big full table cron computes.
Is there a recommended approach to expose vote counts for scoring calculations while maintaining the aggregate's performance benefits for display?
This is more of a table architecture question. Thanks !
1 Reply
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!