April 24, 2013 at 4:40 am
tl;dr
April 25, 2013 at 9:34 am
Thanks Tom, got it but it took a while.
Not all gray hairs are Dinosaurs!
April 26, 2013 at 12:39 am
Long question, but interesting.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 26, 2013 at 1:38 am
Carlo Romagnano (4/23/2013)
What is the difference between the answer 3 and 6?5, 3, 1
I don't think there is any. But the answers may tell us two interesting things: (i) when two answers are the same, more people pick the first than the second; (ii) even when people know only one item on the list can be right, a few will still pick one of a pair of duplicate entries. Of course the number of responses that pick one of those two (only about 60 so far) may be so small that it doesn't reliably tell us anything.
Actually, I suspect that one of those was a typing error on my part and should have been 5,3,2. But I'm not sure - I was trying to complicate things at the time and two equal options might have struck me as an amusing complication, although I don't remember it.
Tom
April 29, 2013 at 2:15 am
Nice question. But little bit lengthy code.
Malleswarareddy
I.T.Analyst
MCITP(70-451)
April 30, 2013 at 7:44 am
The idea for qotd is OK, but a script is too complicated to figure out the result within few minutes I'm willing to spend on it.
There are a lot of mistakes, typos and non standard syntax.
--***** tidy up part 1: drop the views and table created above *****
delete dbo.tmp1 --missing "v" -ok, a typo
go
delete dbo.vtmp
go
delete dbo.tmp1
--missing "go"
Delete statement deletes data, does not drop the table/view.
Standard syntax for delete statement is DELETE FROM Table. In transact-sql you can skip FROM keyword, but unless you plan to stick with mssql for the rest of your life, forget shortcuts and use standard syntax.
SQL code should be as simple as possible. Meaning: avoid the chain logic if possible (A triggers B, which triggers C or A, which then triggers D). If not possible, at least document the logic with embedded comments.
Hope you'll do better next time.
April 30, 2013 at 5:26 pm
Robert-378556 (4/30/2013)
The idea for qotd is OK, but a script is too complicated to figure out the result within few minutes I'm willing to spend on it.
See earlier post which points out why is is as complicated as it is. I agree it's too complicated. But I don't think it's too complicated to get the result in a few minutes, just that it's sufficiently complicated that it will take a few minutes of hard thinking (which is too complicated for QotD).
There are a lot of mistakes, typos and non standard syntax.
....
the "missing" go is redundant, so not missing.
Delete statement deletes data, does not drop the table/view.
Stupid error on my part. Obviously my brain wasn't working properly there. Or maybe my fingers. I should copy and paste from my test harness, instead of retyping - the views and table are gone from my sandpit, so I must have had drop view and drop table statements there.
Standard syntax for delete statement is DELETE FROM Table. In transact-sql you can skip FROM keyword, but unless you plan to stick with mssql for the rest of your life, forget shortcuts and use standard syntax.
I don't expect to use a different RDBMS ever again, unless I get around to sorting out the cross-statement spool issue so that I can write a strictly declarative toy RDBMS. And anyway, I acquired the habit of leaving out that redundant FROM long before MSSQL existed, so there must be [or at least have been] another RDBMS that allowed me to leave it out.
SQL code should be as simple as possible. Meaning: avoid the chain logic if possible (A triggers B, which triggers C or A, which then triggers D). If not possible, at least document the logic with embedded comments.
Trouble with embedded comments in a QotD is that there would be a serious risk that the answer will be in the comments. And the trouble with trying to avoid chain logic (trigger causes another trigger) is quite simply that without it is impossible to talk about nested triggers, so the topic stated for this question should have indicated that your comment on that topic was somehat pointless.
Hope you'll do better next time.
I'm afraid the next one is probably just as bad (apart from delete instead of drop, I hope: the system on SQLServerCentral doesn't allow me to see my question after it's accepted until it's published, so I can't be sure). After that I'll maybe revert to my old question style and submit things that test knowledge and not ability to execute code in one's head (instead of things that try to test both). Or maybe not - maybe it's not a bad thing for a QotD to require 5 minutes hard thinking?
Tom
May 7, 2013 at 2:01 am
Gosh. This question should be appeared in "question of the week" rather than "question of the day". Too lengthy. Don't know if only i felt this little heat. But after spending some good 20 odd minutes, got this correct. 🙂
May 7, 2013 at 5:23 am
L' Eomot Inversé (4/30/2013)
After that I'll maybe revert to my old question style and submit things that test knowledge and not ability to execute code in one's head (instead of things that try to test both). Or maybe not - maybe it's not a bad thing for a QotD to require 5 minutes hard thinking?
Purpose of qotd is to have fun, test knowledge and learn something.
I'm very busy, so on a tilt I go to do something different (read news, qotd, walk,...), during any of these activities I do not appreciate requirement to do 5 minutes of hard thinking of the same kind I got the tilt from. 😀
May 31, 2013 at 1:20 am
more than 20 lines in the questions ? remains two possible actions :
1) copy / code and runs in SSMS and then quietly report the answer to get 1 point
2) randomly try one of the choice
I definitly don't want to use the first choice and had a bad guess
luckyless !
Viewing 10 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply