[Progress Communities] [Progress OpenEdge ABL] Forum Post: Using -rereadnolock with ROWIDs

  • Thread starter Thread starter Jeff Ledbetter
  • Start date Start date
Status
Not open for further replies.
J

Jeff Ledbetter

Guest
Hi. We are trying to understand this kbase: Progress KB - The rereadnolock session startup parameter does not always cause a NO-LOCK records to be re-read from the database. Specifically: "There are several contexts where the -rereadnolock startup parameter has no effect on NO-LOCK record reads. In the following cases, the -rereadnolock startup parameter will not cause the record to be re-read from the database: 1. The -rereadnolock parameter has no affect on records that are being retrieved via RECID or ROWID . In this case, Progress will not re-read the record. It will use the copy of the record already stored in the buffer. If the most current version of the record is needed instead, then use the RELEASE statement on all buffers that contain a copy of the record before reading the record, or use FIND CURRENT or GET CURRENT statements to re-read the record." Does that mean that if I have a session using -rereadnolock and call the code below giving it customer ROWID, there is a chance that it may get the record from the ICB instead of the database? PROCEDURE doIt: DEFINE INPUT PARAMETER prCust AS ROWID NO-UNDO. DEFINE BUFFER bCust FOR customer. FIND bCust NO-LOCK WHERE ROWID(bCust) = prCust. /* do something */ END PROCEDURE.

Continue reading...
 
Status
Not open for further replies.
Back
Top