January 8, 2013 at 8:21 pm
January 8, 2013 at 9:44 pm
Nice question - I wonder if the question category should have been table aliases instead of joins
Thanks,
Andre Ranieri
January 8, 2013 at 10:21 pm
Nice Question. Thanks!
~ Lokesh Vij
Link to my Blog Post --> www.SQLPathy.com[/url]
Follow me @Twitter
January 8, 2013 at 11:07 pm
Andre Ranieri (1/8/2013)
Nice question - I wonder if the question category should have been table aliases instead of joinsThanks,
Andre Ranieri
+1
--
Dineshbabu
Desire to learn new things..
January 8, 2013 at 11:57 pm
Not sure what this question tries to teach us.
I spend 5 minutes looking for a mistake, only to finally decide there wasn't one, all joins seemed legit. I got it right, but I suddenly was surprised the question was about table aliases.
Maybe I was more surprised that apparently the criteria for a query to run succesfully is to get your table aliases correct
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 9, 2013 at 12:05 am
Dineshbabu (1/8/2013)
Andre Ranieri (1/8/2013)
Nice question - I wonder if the question category should have been table aliases instead of joinsThanks,
Andre Ranieri
+1
I agree with both Andre and Dineshbabu. Was looking for any issues in the joins for couple of minutes but found no issues.
January 9, 2013 at 12:30 am
Koen Verbeeck (1/8/2013)
Not sure what this question tries to teach us.I spend 5 minutes looking for a mistake, only to finally decide there wasn't one, all joins seemed legit. I got it right, but I suddenly was surprised the question was about table aliases.
Maybe I was more surprised that apparently the criteria for a query to run succesfully is to get your table aliases correct
+1
January 9, 2013 at 12:58 am
Koen Verbeeck (1/8/2013)
Not sure what this question tries to teach us.I spend 5 minutes looking for a mistake, only to finally decide there wasn't one, all joins seemed legit. I got it right, but I suddenly was surprised the question was about table aliases.
Maybe I was more surprised that apparently the criteria for a query to run succesfully is to get your table aliases correct
Boh?!!:smooooth:
January 9, 2013 at 1:50 am
Thanks for the question - and the easy point.
-------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a question
There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
I would never join a club that would allow me as a member - Groucho Marx
January 9, 2013 at 3:33 am
Koen Verbeeck (1/8/2013)
Not sure what this question tries to teach us.I spend 5 minutes looking for a mistake, only to finally decide there wasn't one, all joins seemed legit. I got it right, but I suddenly was surprised the question was about table aliases.
Maybe I was more surprised that apparently the criteria for a query to run succesfully is to get your table aliases correct
Couldn't see a problem in the syntax but went for no as I couldn't see the point of the answer being yes!
January 9, 2013 at 5:07 am
Couldn't see a problem in the syntax but went for no as I couldn't see the point of the answer being yes!
Me too :unsure:
January 9, 2013 at 5:22 am
Thanks for the question.
January 9, 2013 at 6:21 am
Saw the question title and the SQL and thought this would be a useful question about joins.
Was about disappointed to find it was a yes/no question rather than about the expected results (how many would have been caught out by the left join to TT2 with the criterion on that table in the WHERE clause?).
Turned out not to be a question about joins at all, but about table aliases - which makes it even more trivial!
Very strange.
January 9, 2013 at 7:16 am
Koen Verbeeck (1/8/2013)
Not sure what this question tries to teach us....
I guess.. this; if the aliases are been removed in SELECT block, it gives below error on ambiguity for couple of column names. (some sort.... author might had in mind)
Msg 209, Level 16, State 1, Line 3
Ambiguous column name 'Name2'.
Msg 209, Level 16, State 1, Line 4
Ambiguous column name 'Name3'.
(looks like this was one of the "out of the box" experience )
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
Viewing 15 posts - 1 through 15 (of 33 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy