Some random IN vs. NOT IN with T-SQL

-

I'll try to expand on this, but anyway, here's some examples about how you have to be careful with IN and NOT IN in T-SQL in terms of when results will be returned. If the list you're comparing to has nulls, watch out. If the item you're comparing has nulls, watch out. If the list could be empty, check for that. IN and NOT IN may behave differently than you expect in all these situations. Below are most of the iterations.


--in select 'row' where 1 in (1,2,3)--returns select 'row' where 1 in (select 1 union select 2)--returns select 'row' where 1 in (select null union select 2) --does NOT return - cannot determine if 1 "in" null, maybe it is, who knows? select 'row' where 1 in (select top 0 f1 from (select 1 f1 union select 2) qry) --NO return b/c the top 0 qry returns "nothing", and 1 is NOT "in" nothing ("in nothing" = false) --so if the scenario is that you want to return "all" if the list is empty, then you have to add a check like this: select 'row' where --include all if the list is empty not exists (select top 0 f1 from (select 1 f1 union select 2) qry) or --if the list is not empty, return matches only 1 in (select top 0 f1 from (select 1 f1 union select 2) qry) --NOW returns because the list is empty (top 0) --not in select 'row' where 1 not in (1,2,3) --no return select 'row' where 1 not in (select 1 union select 2) --no return select 'row' where 1 not in (select 2 union select 3)--returns select 'row' where 1 not in (select null union select 2) --does NOT return - cannot determine if 1 "not in" null, maybe it is, who knows? select 'row' where 1 not in (select top 0 f1 from (select 1 f1 union select 2) qry) --Returns b/c the top 0 qry returns "nothing", and 1 is "not in" nothing ("not in nothing" = true) --so if the scenario is that you want to return "all" if the list is empty, same "not exists / or" check as above: select 'row' where --include all if the list is empty not exists (select top 5 f1 from (select 1 f1 union select 2) qry) or --if the list is not empty, return matches only 1 NOT in (select top 5 f1 from (select 1 f1 union select 2) qry) --NO return b/c 1 "not in" the exclusion list = true






There you go, happy coding.

Comments

Post a Comment

Popular posts from this blog

SQL 2005 SP4 and MSreplication_subscriptions

-
If you're trying to apply SQL 2005 SP4 (or any SQL service pack), and it's failing, and you're seeing error "MSP Error:  29537  SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Invalid object name 'MSreplication_subscriptions'", then you've hit this bug which Microsoft is currently saying they "Won't Fix": https://connect.microsoft.com/SQLServer/feedback/details/521231/failure-during-server-script-upgrade-process-on-database-in-sp-vupgrade-replication-procedure#tabs Probably you've done one of 2 things: You're using synonyms that match the system replication table names You've got some vestige replication tables laying around in one of your old databases My case was the latter. The fix was to find the vestige tables and get rid of them. I found them using the following script: [sourcecode language="sql"] /* This will detect db's containing vestiges of Replication
Read more

Hiding an ASPXGridView Delete button with HTMLRowCreated vs. CommandButtonInitialize

-
It's pretty typical in Administration forms to need to hide buttons on certain rows for various reasons. Particularly it is nice to hide the Delete button if in fact the row in question is being used in other places in the app. This is a nice feature to let the user know up front that the row in question is in use, rather than them trying to delete it and getting a foreign key related error after the fact. For years now in DevExpress ASPxGridView's I have been handling this in the HtmlRowCreated event. And I have been doing it wrong. Before: protected void gridGiftCodes_HtmlRowCreated ( object sender, DevExpress.Web.ASPxGridViewTableRowEventArgs e) { if (e.RowType == GridViewRowType.Data){ int commandColumnIndex = - 1 ; //Find the command column commandColumnIndex = e.Row.Cells.Count- 1 ; //assume it's the last visible colum //Get the command cell for this row GridViewTableCommandCell cell = e.Row.Cells[commandColumnIndex] as Gri
Read more

SQL Server Deadlocks - Easy Quick Start Guide

-
If you find the topic of SQL Server deadlocks a little intimidating and mysterious, you are not alone. But fear not, this Quick Start lays out the practical shortcut I bet is sufficient for most scenarios. Definition: What is a Deadlock A deadlock occurs when 2 threads are competing for similar resources, and Thread 1 HAS A and WANTS B, and Thread 2 HAS B and WANTS A. They’re stuck. SQL Server picks a loser and throws error 1205 "Transaction... has been chosen as the deadlock victim." The BIG PROBLEM if your application has a lot of deadlocks is unpredictable application behavior . This can especially show up in apps that call large stored procs where the failing statement gets rolled back, but the proc itself may just keep on trucking with the next statement. This is all based on what kind of error handling you're doing, whether you have XACT_ABORT on, whether you're doing explicit transactions with BEGIN TRAN or not, etc. Very Probably your application is no
Read more