RE: best practice for web client updates to multiple tables -- MIDRANGE-L

Subject: RE: best practice for web client updates to multiple tables
From: rob@xxxxxxxxx
Date: Wed, 8 Jan 2014 07:58:21 -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>

IOW, instead of doing an RPG read without a lock where you manually add x
to ONHAND and then do an update, you do
update ... set onhand=onhand+x where...
then the row is locked until the COMMIT.
If he ran the update ... WITH NC then he's obviously trying to run outside
of commitment control and can't run the ROLLBACK so it's rather moot.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

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.