Adding a row to a column set

  • Comments posted to this topic are about the item Adding a row to a column set

  • Nice question, thanks, Steve

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

  • Shouldn't the query read 'WHERE uc.UserID = 8'?

  • ildjarn.is.dead - Tuesday, September 11, 2018 12:37 AM

    Shouldn't the query read 'WHERE uc.UserID = 8'?

    That thought did occur to me as well.
    It is still a good question, despite that.....

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

  • Stewart "Arturius" Campbell - Tuesday, September 11, 2018 12:43 AM

    ildjarn.is.dead - Tuesday, September 11, 2018 12:37 AM

    Shouldn't the query read 'WHERE uc.UserID = 8'?

    That thought did occur to me as well.
    It is still a good question, despite that.....

    How can it be a good question if it's a terrible question?

  • I've got it right, but the first and second answer seems to be equal!
    Can someone  clearyfy me?
  • Carlo Romagnano - Tuesday, September 11, 2018 1:14 AM

    I've got it right, but the first and second answer seems to be equal!
    Can someone  clearyfy me?

    The three sparse columns aren't returned, so 'all columns' isn't correct.

  • Thanks Steve,
    I had no idea about Column Sets before today, so your question has done exactly what it should - expand my knowledge. Perfect.
    Andy

  • Queries as written return no data whatsoever, so none of the answers is correct, surely?

  • Giles Sutcliffe - Tuesday, September 11, 2018 2:20 AM

    Queries as written return no data whatsoever, so none of the answers is correct, surely?

    That's the option I was looking for.

  • Giles Sutcliffe - Tuesday, September 11, 2018 2:20 AM

    Queries as written return no data whatsoever, so none of the answers is correct, surely?

    You aren't correct! The query returns an empty resultset with the columns and types defined in the first answer.

  • Carlo Romagnano - Tuesday, September 11, 2018 2:55 AM

    Giles Sutcliffe - Tuesday, September 11, 2018 2:20 AM

    Queries as written return no data whatsoever, so none of the answers is correct, surely?

    You aren't correct! The query returns an empty resultset with the columns and types defined in the first answer.

    Not on my box it didn't!

  • Carlo Romagnano - Tuesday, September 11, 2018 2:55 AM

    Giles Sutcliffe - Tuesday, September 11, 2018 2:20 AM

    Queries as written return no data whatsoever, so none of the answers is correct, surely?

    You aren't correct! The query returns an empty resultset with the columns and types defined in the first answer.

    The UserConfigKey, the UserID, and the Options column with 3 XML nodes.

    The options column contains nothing. Option 1 says it contains 3 XML nodes. None of the answers is correct.

  • Since you're filtering on an identity column which would only have the value 1, why would any data be returned?

  • Actually no rows are returned.  I guessed the first answer correctly.  The WHERE clause needs to be changed.

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

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