Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Anton Shepelev <anton.txt@g{oogle}mail.com>
Newsgroups: comp.databases.ms-sqlserver
Subject: Re: UPDATE FROM
Date: Mon, 19 Jul 2021 17:21:38 +0300
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <20210719172138.5d4e4628fc7454f1c19fc659@g{oogle}mail.com>
References: <20210719121448.6ece4302949ccaaee268158c@g{oogle}mail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: reader02.eternal-september.org; posting-host="dd0fec3c51854a8499957acc1fda1d80"; logging-data="31493"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18Sgw5jr+51kSvPxDZ3ZhXI5pny1Qvwn9c="
Cancel-Lock: sha1:qY0/zQ9oi7fIZRVArClEy1VeVGs=
X-Newsreader: Sylpheed 3.5.0 (GTK+ 2.24.23; i686-pc-mingw32)
Xref: csiph.com comp.databases.ms-sqlserver:2094

Question withdrawn. It was an error in my logic, whereas
the syntax is quite clear. The simplest UPDATED from another
table does *not* requre that it the table begin updated be
mentioned in the FROM clause:

  UPDATE upd_tab
  SET col = data_tab.col
  FROM data_tab
  WHERE data_tab.code = upd_tab.code

-- 
()  ascii ribbon campaign - against html e-mail
/\  http://preview.tinyurl.com/qcy6mjc [archived]