Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Can anyone think of a reason to do this:
SELECT * FROM TableA ORDER BY cast(cast(RealColumnA as nvarchar(50))as float) –where RealColumnA is defined as real in the table
A former developer of mine insisted this was necessary to get reals to sort correctly. Can anyone think of a reason that may be true?
The cast in the orderby clause is a big performance killer. But I need to be sure it is not necessary before I remove it.
Remove it. ORDER BY is what you expect it to be. And it certainly would be a performance killer.
Rule #1 about SQL. Question (and test) all your (and other peoples’) assumptions. (Especially weird ones like this.)