-
Friday, January 21, 2005
Ok, so in my last post, it turns out there are better ways to do some of what I was talking about. Unfortunately though, I have gotten a new "fan" who thinks I'm an idiot. I'm sure he's right about the fact that using ISNULL doesn't use an index. Good for you Thomas, I learned something new, thank you. But seriously, that blog entry was just about the worst presentation of correcting someone I have EVER seen. I mean even at the end of the entry he points out that I've written for a book, implying it's probably a crappy
-
Friday, January 21, 2005
Here's just a quick tip I came across (this is actually a good read on Whidbey Data Beta 2 features), which is pretty handy (and not so obvious) even if that's not what the article is really about. If you have a field in a table that you need to search on, but the field allows nulls AND you want to be able to ignore the field completely, then check out this example: CREATE PROCEDURE dbo.FindCustomers( @FirstName varchar(50), @LastName varchar(50), @Email varchar(100), @Age tinyint)ASSELECT CustomerID, FirstName, LastName, Email, AgeFROM CustomersWHERE FirstName = ISNULL(@FirstName, FirstName) AND LastName = ISNULL(@LastName, LastName) AND Email = ISNULL(@Email,
-
Friday, January 21, 2005
As pointed out by Mike Krisher! How exciting is that? ;) Seriously though, Mike has some good points about it being more our city's leaders than the actual people (if there's some accuracy in it at all of course). I will admit I've met some pretty dumb people in this town, but I've also met a ton of really smart people! To my defense, I've only lived in this town since September. Although, I grew up not 25 miles from here! ;)