|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Today @ 12:54 AM
Points: 1,969,
Visits: 1,820
|
|
| Comments posted to this topic are about the item CASTing
|
|
|
|
|
SSCarpal Tunnel
       
Group: General Forum Members
Last Login: Today @ 4:10 AM
Points: 4,422,
Visits: 7,178
|
|
Sorry, I don't understand. What CAST to nvarchar(800)? Is there a typo in the question?
John
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 3:02 PM
Points: 768,
Visits: 1,159
|
|
me a little bit confused too, what's the difference between this Question, and the one 2 days ago?
TODAY
CASTing
Second question of day: what is the len of @c?
declare @c varchar(800)
set @c = N'hello' + replicate('-',800) print len(@c) print @c Sorry - you were wrong
Correct answer: 800 Explanation: The CAST to nvarchar(800) has a maximum 4000 character len. The CAST then to varchar(800) fits in that space, so the len is 800
2 days ago
CASTing
First question of day: what is the len of @c?
declare @c varchar(8000)
set @c = N'hello' + replicate('-',8000) print len(@c) print @c
You got it right!
Correct answer: 4000 Explanation: The CAST to NVARCHAR(4000) means that the maximum len is 4000, then the cast to varchar(8000) allows more characters, but the string is already truncated.
SQLServerNewbie
MCITP: Database Administrator SQL Server 2005
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 7:42 AM
Points: 2,802,
Visits: 7,103
|
|
| The one two days ago was casting to a length greater than the nvarchar data type max of 4000, so the length was truncated to 4000. The one today was casting to a length less than 4000 so it stayed the same.
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 3:02 PM
Points: 768,
Visits: 1,159
|
|
Does that mean this 2 lines below, converts @c to nvarchar(8000)? meaning ANY casting to nvarchar always give it maximum length of 8000?
declare @c varchar(800) set @c = N'hello'
I think I got lost by reading this sentence ... maybe I shouldn't read it anymore
The CAST to nvarchar(800) has a maximum 4000 character len.
SQLServerNewbie
MCITP: Database Administrator SQL Server 2005
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 7:42 AM
Points: 2,802,
Visits: 7,103
|
|
nvarchar has a max length of 4000 not 8000 the 'N' in this statment converts it;
set @c = N'hello'
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Yesterday @ 4:06 PM
Points: 1,409,
Visits: 2,027
|
|
Good question of the day...I totally fell for it!
Jason Shadonix MCTS, SQL 2005
|
|
|
|
|
SSCarpal Tunnel
       
Group: General Forum Members
Last Login: Today @ 4:10 AM
Points: 4,422,
Visits: 7,178
|
|
Yeah, so did I. I see what happened now.
John
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, July 13, 2011 2:21 AM
Points: 251,
Visits: 208
|
|
Great question.
Didn't fall into the trap, but only because I remembered the question 2 days ago and thought there must be something else going on.
Its got me thinking a lot more about types and implicit conversions. Thanks
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Today @ 1:06 AM
Points: 2,525,
Visits: 3,618
|
|
I think these two QODs really show how evil implicit type conversions are. Id rather spend this one second on explicit type conversion than on reviewing such code for possible data loss caused by implicit conversion. I had to look at this QOD for at least 5 seconds before I made my choice. Sum this up for all your code and then tell me: wouldn't it be great if the compiler told you when you had missed a type conversion?
Sure, you have a test team, but why not catch an error in the first place? Isn't a database a realm where datatypes should be handled in the most strict way?
Just some thoughts in the late evening
Best Regards,
Chris Büttner
|
|
|
|