1

On Visual Studio 2019 SSDT. Inside a procedure we have:

create table a (test1 varchar(50))
create table #b (test2 varchar(50))

select a.nop from a

select a.nop from a, #b b where a.test1 = b.test2

The first select gives a warning of columns missing, but the second one doesn't. Is any configuration available to force a warning (or error) on the second select? The moment a temp table is present visual allows anything, even when the missing field has the "a."

4

0 回答 0