Post reply

TSQL "where - 101"

  • November 11, 2014 at 9:31 pm

    #291947

    Comments posted to this topic are about the item TSQL "where - 101"

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

  • November 11, 2014 at 10:23 pm

    #1757826

    Very Easy 🙂

  • November 12, 2014 at 12:57 am

    #1757835

    Nice 'n' eazy.

    Thanks & Best Regards,
    Hany Helmy
    SQL Server Database Consultant

  • November 12, 2014 at 1:36 am

    #1757844

    None of the answers are correct when you take into account the names are with a capital and the answers are lower case, the question was to give all names from the table, answer 3 and 4 do this. Never was the question to give all names duplicates included. Question could be better worded.

  • November 12, 2014 at 2:21 am

    #1757850

    Both choice 3 and 4 is correct.Because author does not say duplicate names are ok.:crazy:

  • November 12, 2014 at 2:27 am

    This was removed by the editor as SPAM

  • November 12, 2014 at 2:32 am

    #1757855

    Stewart "Arturius" Campbell (11/12/2014)

    Good question, thanks Stuart

    erwin.oosterhoorn (11/12/2014)

    None of the answers are correct when you take into account the names are with a capital and the answers are lower case, the question was to give all names from the table, answer 3 and 4 do this. Never was the question to give all names duplicates included. Question could be better worded.

    That would depend on the case sensitivity / collation of the database you are working in.

    It was sparked by new dev here, who couldn't see the difference between any of the four possible answers :w00t:

    As the question and answer showed mixed cases, case insensitivity is implied, again something missed by our now ex dev.

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

  • November 12, 2014 at 2:38 am

    #1757859

    The question said "every employee", that should be clear enough, one record per employee. If you DISTINCT, you get list of peoples names, not people.

    "There's Brian over there, and that's another Brian here. But they are both the same, so make them one cup of tea between them"

  • November 12, 2014 at 3:06 am

    #1757867

    Nice basic question

  • November 12, 2014 at 3:44 am

    #1757886

    Mark Grout (11/12/2014)

    The question said "every employee", that should be clear enough, one record per employee. If you DISTINCT, you get list of peoples names, not people.

    "There's Brian over there, and that's another Brian here. But they are both the same, so make them one cup of tea between them"

    I agree. There are no need to fuzz over the question being "worded badly" as erwin.oosterhoorn and vivekjamshedpur says..

  • November 12, 2014 at 3:49 am

    #1757889

    Stuart Davies (11/12/2014)

    It was sparked by new dev here, who couldn't see the difference between any of the four possible answers :w00t:

    As the question and answer showed mixed cases, case insensitivity is implied, again something missed by our now ex dev.

    I cringe when I read this. A new dev who have no clue about boolean expressions. No wonder you name him/her "our now ex dev", because that's a steep hill, this one is trying to climb!

  • November 12, 2014 at 4:45 am

    #1757914

    Thanks for the question.

    ---------------
    Mel. 😎

  • November 12, 2014 at 4:46 am

    #1757915

    Mark Grout (11/12/2014)

    The question said "every employee", that should be clear enough, one record per employee. If you DISTINCT, you get list of peoples names, not people.

    "There's Brian over there, and that's another Brian here. But they are both the same, so make them one cup of tea between them"

    +1

    ---------------
    Mel. 😎

  • November 12, 2014 at 5:29 am

    #1757923

    Stuart Davies (11/12/2014)

    It was sparked by new dev here, who couldn't see the difference between any of the four possible answers :w00t:

    As the question and answer showed mixed cases, case insensitivity is implied, again something missed by our now ex dev.

    And here I was reading them thinking to myself that it must have been strange trying to come up with the wrong answers. Granted, we see a lot of stuff in our own systems and here, but for something so simple, it must have been weird. A nice, simple, unambiguous question, Stuart. Thanks.

    Tally Tables - Performance Personified
    String Splitting with True Performance
    Best practices on how to ask questions

  • November 12, 2014 at 5:30 am

    #1757925

    vivekjamshedpur (11/12/2014)

    Both choice 3 and 4 is correct.Because author does not say duplicate names are ok.:crazy:

    No, they aren't. He even bolded the word "all" in the question. Even without bolding it, it would have still meant the same thing.

    Tally Tables - Performance Personified
    String Splitting with True Performance
    Best practices on how to ask questions

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

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