This makes no sense

vbboyd · May 21st, 2013, 12:31 AM

Why is it that when I run the following query against your database in the SQL Server management studio:

Code:

select * from Genre 
where Name Like "Pop"

I get the following error:
Msg 207, Level 16, State 1, Line 2
Invalid column name 'Pop'.
I get the same error message with the following query as well.

Code:

select Id from Genre 
where Name like "Pop%"

Isn't that the way a that like statement is supposed to look like??? Am I missing something here???!!! I am noting short of super confused on this one like you wouldn't believe. Any help on this would be so greatly appreciated.

Imar · May 21st, 2013, 02:12 AM

Take another look at the section "Filtering data" on page 429; you're using the wrong type of quotes.

Cheers,

Imar

vbboyd · May 21st, 2013, 08:08 AM

Quote:

Originally Posted by Imar

Take another look at the section "Filtering data" on page 429; you're using the wrong type of quotes.

Cheers,

Imar

Yeah I know. I using a book that for Transact SQL that was published in 1997, and it showed the like phrase being used with the "" quotes. It wasn't until I looked at an example in your book that it finally worked. But it was really a head scratcher for a while for sure. I have been using LINQ with entity framework for so long that I have gotten totally out of practice with just using plain ole standard SQL queries. So with that being the case, do you think that standard SQL queries will become a thing of the past in .NET application development of the future?

Imar · May 21st, 2013, 01:24 PM

No, I don't think so. I think there will be room for both....

Imar