I forgot to mention this is in SQL Server, so SIN operates on radians. So I THINK this can only ever cast to a 0 when clientId
is also 0
It certainly doesn't for any of the 100,000 existing rows
I think it is a bug and here's why
I have setup a lemmy instance to understand how it works and hopefully contribute something meaningful
My instance has 2 users, both are subscribed to the same cross-instance community, but only one is showing Subscribe Pending
even if I un-sub and re-sub
I am not aware of any approval system to subscribe to a community, so I believe the approval was received the community instance, but the "accept" response data was missed / dropped when returning to your host instance
Update: The original dev does not remember exactly. However they have said that
clientId
was originally a VARCHAR, so this may have been checking for both'0'
or''
So an over-engineered workaround to a bad datatype perhaps?