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
Guess the intent
Paged Out! is a free experimental technical magazine
Hacking Millions of Modems (and Investigating Who Hacked My Modem)
Programming Music
2039 - Tom Mauritzon
Eclipse compiler issue
Anyone need a gift from the River Vivillon region?
Update: The original dev does not remember exactly. However they have said that
clientIdwas originally a VARCHAR, so this may have been checking for both'0'or''So an over-engineered workaround to a bad datatype perhaps?