Bug in "Qualify Object Names" introduced bug in my code!

SELECT  onfile.DealReference  
                    dbo.DCA_Detail AS onfile 
                    WHERE   onfile.DealReference NOT IN &#40;  
                            SELECT  DealReference  
                            FROM    #tmpAllocatedDealReferences &#41;

When I chose to "Qualify Object Names", it changed the subselect as follows.

NOT IN &#40;  
                            SELECT  onfile.DealReference  
                            FROM    #tmpAllocatedDealReferences &#41;

This introduced a nasty little bug, quite tricky to spot.

The DealReference field in the subselect should refer to the temp table.

I'd advise to all that you shouldn't consider the "Qualify Object Names" as purely cosmetic i.e. that if you're going to use it, make sure that you do so BEFORE testing.

Regards,

David McKinney.

dmckinney January 13, 2011 02:45

Comments

2 comments

Hi David

the same occurs with table variables:
```
DECLARE @PP TABLE &#40; PPi VARCHAR&#40;15&#41; &#41;
SELECT PPi FROM @PP
```
after qualifying:
```
DECLARE @PP TABLE &#40; PPi VARCHAR&#40;15&#41; &#41;
SELECT @PP.PPi FROM @PP
```
Qualify inserts @PP. into the select. This creates the error.

JÃ¼rgen
bauerju July 19, 2011 07:05

0
Was this ever fixed?

rlively April 14, 2015 15:10

0

Add comment

Please sign in to leave a comment.

How can we help you today?

Bug in &quot;Qualify Object Names&quot; introduced bug in my code!

Comments