RE: Modernizing applications -- MIDRANGE-L

Subject: RE: Modernizing applications
From: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
Date: Fri, 21 Aug 2009 11:44:46 -0400
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>

I always run the selection criteria through SELECT first and verify

the results

before updating. Does not matter the database (DB2 with or without
journaling/commitment control, SQL Server, etc.).

Doesn't always help. You may have to subtly change the query to make it
an update instead of a select. Now, if you're journaling you do the
select, determine that 44 rows should be updated, start a transaction,
do the update, see that 440 rows were updated, say "ooops" and rollback.
No harm no foul. Or commit if the right number of rows were updated.

-Walden

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.