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?
0589 6066 6425
I would love to give gifts to anyone here
I am from Australia, and I travel between Queensland and South Australia regularly
This is in my nearby list
This is in my profile
No worries at all
Let me make sure I understand first
i added my private key, and tried to connect
This concerns me, as the server should have the user's public key, not private. Private should be exactly that, private
Is the Powershell user / SSH key the same as the Putty user / SSH key that still works?
When you run the Powershell script, does it give any error messages?
I know with Linux -> Linux SSH you can log verbosely with -v
, is that something you can do under Powershell?
Is password auth enabled? Does that still work from Putty, and can you do the same from Powershell?
Yeah mate, you are right "doesn't work" is pretty useless, lucky I didn't say that
I said I have code that does compile in one specific compiler but doesn't in another specific one, and asked if anyone had ever encountered that before
And 2 days ago when someone mentioned that I didn't include the actual error, I apologised and then included it
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?