Is it possible for us to only have one op per userID?

For sqlite operations, we typically have a pattern of a single op per single replace.

I did introduce some grouping logic in https://phab.comm.dev/D11298 that would group together any successive replace operations paired with a replace op in sqlite that took multiple entries, but it's not standard in our codebase.

If we did want to have a single op do this, we'd need to introduce a new sqlite operation.

I was curious on implementing this if there'd be a noticeable performance decline as we're doing this for our entire user store (for anyone with a non-null fid).

If you think we should make the necessary sqlite additions/modifications, I can create a follow up task

To clarify, we could also just remove the previous replace operation and make all actions use the multiple entry replace operation, so not technically a full new sqlite op but a rewrite of a portion of it

@ashoat I realize I read your question wrong.

I think we can definitely do one op per userID. We'd first update with the new farcaster fids in a first loop.

In the second loop, we only clear if the userID wasn't in action.payload.farcasterUsers

I think we can set the farcaster userIDs into a set so that we can easily lookup if it doesn't require an fid clear in the second loop