fill out followee_reposts and followee_favorites fields #9
Conversation
stereosteve
force-pushed
the
followee_reposts
branch
from
e993444 to
535eeef
Compare
stereosteve
left a comment
stereosteve
left a comment
There was a problem hiding this comment.
Great work Steve!
| // todo: fill this out | ||
| // hide these GetTrackRow fields | ||
| FolloweeFavoriteIds any `json:"followee_favorite_ids,omitempty"` | ||
| FolloweeRepostIds any `json:"followee_repost_ids,omitempty"` |
There was a problem hiding this comment.
get_tracks.sql adds these fields with list of user IDs. Here we hide them by shadowing the fields from the embedded GetTrackRow struct and making them omitempty.
| } | ||
| for _, id := range track.FolloweeRepostIds { | ||
| userIds = append(userIds, id) | ||
| } |
There was a problem hiding this comment.
this list of users IDs (owner, known reposters, know savers) across all tracks can have duplicates... but we're passing it into sql land with where user_id = ANY(@ids) type of thing... sql does set stuff and so we incur near zero cost for duplicates.
This is why I skip de-dupe on this list and other similar id lists used in a set based context.
| AND saves.is_delete = false | ||
| ORDER BY follower_count DESC | ||
| LIMIT 10 | ||
| )::int[] as followee_favorite_ids, |
There was a problem hiding this comment.
::int[] helps sqlc choose []int32 for generated struct (instead of interface{} aka any)
stereosteve
force-pushed
the
followee_reposts
branch
from
535eeef to
7df15fe
Compare
No description provided.