in reply to Pulling a blank SQL row, but there are no blank rows.

Probably not helpful but you could add a check to verify that the fetching does not fail (check @Quote for defined-ness).

And I find the order by clause a bit strange: Why do you add backets to the newid - is a SQL-server speciality?

And by the way: Why do you not use the SQL in $Statment but rather repeat it again?

And is there anything wrong in using lower-case variable names and normal quotation marks just like everyone else does?

  • Comment on Re: Pulling a blank SQL row, but there are no blank rows.

Replies are listed 'Best First'.
Re^2: Pulling a blank SQL row, but there are no blank rows.
by MatthewV (Acolyte) on Jun 14, 2009 at 01:49 UTC
    And I find the order by clause a bit strange: Why do you add backets to the newid - is a SQL-server speciality? That is just the way the SQL command is used.
    And by the way: Why do you not use the SQL in $Statment but rather repeat it again? Old line of code form a test I was doing, thank for poiting it out I have removed it.
    And is there anything wrong in using lower-case variable names and normal quotation marks just like everyone else does?My coding style is to make the first letter of all words in a varible uper-case, just an old habbit. Not sure what you mean by "normal quotation marks"
    Probably not helpful but you could add a check to verify that the fetching does not fail (check @Quote for defined-ness).I could add a check to see if the array gets filled or not but what would I do if it did not? The point of this code is to grab a random quote from the DB and display it so I need to figure out why a blank quote is being grabed.
      Just for curiosity:

      Is there any difference (in SQL server) between

      select top 1 Quote, CharacterName, GameTitle from dbo.GameQuotes order + by newid()
      and
      select top 1 Quote, CharacterName, GameTitle from dbo.GameQuotes order + by newid
      i.e. without the parentheses at the end of newid?