InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 05:01:39 GMT20http://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxI got the result by executing the each statement :)Sat, 02 Feb 2013 03:20:32 GMTudayroy15http://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxreally very tough one...Fri, 11 Jan 2013 11:53:48 GMTmanik123http://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspx[quote][b]john.arnott (1/8/2013)[/b][hr]How annoying. You made me think! ;) I agree this was an excellent question and explanation. I do see that one minor correction could be needed to one example given, however. You say "...for example the numeric value 37.2 can be converted to an int (37)...". Did you actually mean that an INT (@i) could be converted to the higher precedence numeric type, as obviously could be the literal value 37.2? After all, the result of that coalesce is 37.2 and not 37.[/quote]yes, I did. Obviously my check-reading what I had written wasn't up to scratch that day. :blush:Thu, 10 Jan 2013 10:47:35 GMTL' Eomot Inverséhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxGreat QoTD..Thanks..Wed, 09 Jan 2013 18:51:52 GMTpchiragshttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxThanks for the great question Tom. It really made me think; there were so many choices and it was so early in the morning. I can definitely say I'm awake now. :-DWed, 09 Jan 2013 07:35:00 GMTDana Medleyhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxInteresting question, thank you Tom.(even kind of knowing the output for each select statement, it tempted me to challenge self and to prove it)Wed, 09 Jan 2013 07:03:03 GMTRaghavendra Mudugalhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxGreat question, must say. +1Wed, 09 Jan 2013 00:01:12 GMTsqlnaivehttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxthanks good and very tough question!Tue, 08 Jan 2013 22:20:29 GMTjvachttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxVery nice question Tom. Learnt something new today:-)Tue, 08 Jan 2013 22:07:41 GMTLokesh Vijhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxA really good QotD. Thanks, Tom!Tue, 08 Jan 2013 12:07:57 GMTRevenanthttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxHow annoying. You made me think! ;) I agree this was an excellent question and explanation. I do see that one minor correction could be needed to one example given, however. You say "...for example the numeric value 37.2 can be converted to an int (37)...". Did you actually mean that an INT (@i) could be converted to the higher precedence numeric type, as obviously could be the literal value 37.2? After all, the result of that coalesce is 37.2 and not 37.Tue, 08 Jan 2013 10:32:57 GMTjohn.arnotthttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxExcellent question, and great explanation! Thanks!Tue, 08 Jan 2013 09:14:16 GMTRob Schripsemahttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxTripped myself on this one.Thanks Tom, learned something today, so I guess that makes it worthwhileTue, 08 Jan 2013 08:25:41 GMTStewart "Arturius" Campbellhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxGood question Tom. Good to have a refresher on these things from time to time.Tue, 08 Jan 2013 07:20:12 GMTSean Langehttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspx[quote][b]Koen Verbeeck (1/8/2013)[/b][hr]Great and very interesting question. Thanks Tom![/quote]+1 I must agree... was a lot of fun to sit there pondering if all of the various data types would be compatible with each other. Now where did I put that Ibuprofen? hehTue, 08 Jan 2013 06:55:01 GMTmtassinhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxWell, the question is a good one, and I got it right, but if I see code like that I reach for the shot gun.Tue, 08 Jan 2013 04:57:31 GMTRune Bivrinhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxThanks for the great question! A true learning question with no controversy.Tue, 08 Jan 2013 04:12:45 GMT(Bob Brown) http://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxI prefer ISNULL, the cast is done to the first argument.I use it e.g. with numeric type ISNULL(int_null,0). But, I should remember that with string ISNULL may be dangerous as in this case:declare @c varchar(1) select ISNULL(@c,'N/D')Result:N instead of N/DTue, 08 Jan 2013 01:39:11 GMTCarlo Romagnanohttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxGreat and very interesting question. Thanks Tom!Tue, 08 Jan 2013 00:31:29 GMTKoen Verbeeckhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxstill now i thought COALESCE will return the datatype of Non NUll value. Today only i learnt it will consider the highest percedence..Thanks to author for posting nice qstn..Tue, 08 Jan 2013 00:13:25 GMTDineshbabuhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxNice Question. Learnt something for today.Mon, 07 Jan 2013 22:34:21 GMTralshttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxThanks for the question.Mon, 07 Jan 2013 22:07:18 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxI missed it completely :(. no regret , learned something .Also, I am glad to see that on aswering the question, equation for right and wrong is 0% and 100 % Thanks for the question ..Mon, 07 Jan 2013 21:12:04 GMTdemonfoxhttp://www.sqlservercentral.com/Forums/Topic1403953-2681-1.aspxComments posted to this topic are about the item [B]<A HREF="/questions/T-SQL/95543/">Coalesce and Conversion</A>[/B]Mon, 07 Jan 2013 21:07:07 GMTL' Eomot Inversé