Re: Uniquely identifying a record in SQL without a unique key? -- MIDRANGE-L

Subject: Re: Uniquely identifying a record in SQL without a unique key?
From: rob@xxxxxxxxx
Date: Mon, 31 Dec 2012 13:10: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>

When you DECLARE CURSOR you use a SELECT statement. On that SELECT
statement you specify whether or not you are processing it FOR READ ONLY
or FOR FETCH ONLY. So, the same cursor cannot be used to find the row
(without locking it) and then rereading the row with the lock and then
updating it. WHERE CURRENT OF cannot be specified in a cursor opened FOR
FETCH ONLY (aka FOR READ ONLY).

Rob Berendt

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.