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 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
The client
table has around 100,000 rows each with a unique clientId
, none of which are returned from the CAST / ABS / SIN
I think you are right and this is a ‘fix’ for something lost to time. I am going to talk to the original dev tomorrow to see if they remember what it was for
Thank you so much, I’ll check it out!
Absolutely, it’s a great read. Could you link the video you watched?
In the timeline at the bottom it says:
2023-05-05: Converso asks: ‘How were you able to decompile the source code of the app and what do you think should be done to protect against that in the future?’
So I think some of the devs were in way over their heads too!
Not specific to AI, some of the people I work with make me prone to drinking as well
So far really good! It has some quirks, and there are some bugs and some teething issue with the large influx of people (specifically on lemmy.ml)
It is a mind-set change working with a different system and the whole instance
idea is still very new for me
As an Australian, it was very quiet last night (10ish hours ago), but that will improve as more people join
I am not the author, but I found this an amazing write-up
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?