RE: Record by record update with SQL with no matching key. -- MIDRANGE-L

Subject: RE: Record by record update with SQL with no matching key.
From: "Dennis Lovelady" <iseries@xxxxxxxxxxxx>
Date: Tue, 02 Feb 2010 14:21:37 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

update realtable set (first,last,address,city) = (select F1,F2,F3,F4
from faketable, crosstable
where crosstable.fakeid = faketable.id and crosstable.realid =
realtable.realid)

crosstable columns has two columns: realid, fakeid

I think you could do this with rrn() as well.

Interesting. But don't you need a WHERE clause of some sort on the UPDATE
also (not just on the subselect)?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Always live within your income, even if you have to borrow money to do so."
-- Josh Billings

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Record by record update with SQL with no matching key. , Dan Kimmel
Re: Record by record update with SQL with no matching key. , Pete Helgren

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.