Nuance of datetime data type in SQL Server

Question

Nuance of datetime data type in SQL Server

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply

james.brown.iphone Valued Member Points: 63 More actions · Answer 1

Would it not be easier to just cast both variables to the time data type and catch any error (or is there IsTime function?)

GeorgeCopeland SSCertifiable Points: 6997 More actions · Answer 2

james.brown.iphone - Tuesday, April 18, 2017 11:45 AM
Would it not be easier to just cast both variables to the time data type and catch any error (or is there IsTime function?)

Casting a time to a datetime does not throw an error, that is the point of the article. IsDate returns 1 on a valid time value.

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 3

GeorgeCopeland - Thursday, April 13, 2017 1:54 PM
Thinking like this has caused more bugs over the last 70 years than the NULL. It is thinking like this that gave the world Y2K.

Heh... Agreed. And worse than that, it is thinking like this that gave us the crippled DATETIME2 data type, which ultimately gave rise to the need got DATEDIFF_BIG.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)