Printing Dates

Question

Post reply

Printing Dates

Steve Jones - SSC Editor

SSC Guru

Points: 734418
More actions
September 27, 2019 at 12:00 am

#3674535

Comments posted to this topic are about the item Printing Dates

Viewing 15 posts - 1 through 15 (of 20 total)

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

Evgeny Garaev SSCertifiable Points: 7422 More actions · Answer 1

The dates in the question and in the answers do not match 😉

Stewart "Arturius" Campbell SSC Guru Points: 72486 More actions · Answer 2

Nice, easy one, thanks Steve

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”

Nakul Vachhrajani SSChampion Points: 10283 More actions · Answer 3

Wouldn't '2019-01-18 20:23:10' print as Sep 1 2019 8:23 PM? 🙂

Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com

Follow me on
Twitter: @sqltwins

Michael Riemer SSCertifiable Points: 5190 More actions · Answer 4

Michael Riemer

SSCertifiable

Points: 5190

September 27, 2019 at 8:05 am

#3683879

How does 2019-01-18 end up being Sep 1, 2019 too? 😉

DesNorton SSC-Insane Points: 24276 More actions · Answer 5

The correct answer is not available as an option

How to post data/code on a forum to get the best help.

Rune Bivrin SSCrazy Eights Points: 8438 More actions · Answer 6

Looking at the available answers, the only logical response would be that it would fail, since all the other answers have both date and time that doesn't match the input at all. But knowing that PRINT happily works with datetime, I just went ahead and picked the answer with the matching format.

It will be interesting to read Steve's explanation. My guess is he got two QOTD-s mixed up.

Just because you're right doesn't mean everybody else is wrong.

Erwin Oosterhoorn SSCrazy Points: 2289 More actions · Answer 7

Confused, dates do not match but the print answer is wrong as well. Looking forward to the explanation.

edwardwill SSCertifiable Points: 5789 More actions · Answer 8

I agree with all the answers above, apart from Stewart Campbell who not only found it "easy" but apparently has a version of SQL Server that works differently from everyone else's! ;¬}

gary.mazzone SSCarpal Tunnel Points: 4683 More actions · Answer 9

The option answers are all wrong but only 1 is in the proper format so I choose that.

roger.plowman SSChampion Points: 10265 More actions · Answer 10

I think the question is broken, the correct answer is 'Jan 18 2019 8:23PM'

🙂

srienstr SSCrazy Points: 2435 More actions · Answer 11

roger.plowman wrote:

I think the question is broken, the correct answer is 'Jan 18 2019 8:23PM'
🙂

That's what I got when I ran it, after assuming that the date mismatch was a hint that the error was the answer.

Puto me cogitare, ergo puto me esse.
I think that I think, therefore I think that I am.

below86 SSChampion Points: 11510 More actions · Answer 12

We aren't on SQL Server 2017, maybe we don't want to upgrade if this is the type of date conversion you get. Just a joke, since the answers available have to be incorrect.

-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.

gand 29575 SSChasing Mays Points: 617 More actions · Answer 13

Yes, the question and answers do not match. That can only be the true answer.

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

I think this question is an excellent example of why you should never rely on defaults. 😉

--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)