At 09:09 AM 12/4/97 -0500, you wrote:
>Does the execution of an SQL statement (either from an ODBC client or from
>being embedded in an RPG program) lock the record(s) it selects?
>If it does, what needs to be done to free up the file(s) and/or the
>record(s) affected?

Don't know if you'd got any reply yet.

DELETE & UPDATE acquire EXCLUSIVE locks during execution. These are
releases at the next COMMIT, or upon completion, if commitment control is
not in force.

INSERT acquires EXCLUSIVE locks only when commitment control is in force.
Otherwise, no locking is used.

Don't know about the FOR UPDATE OF clause, which, BTW, is AS/400-specific.

Record locking in SQL is closely tied to commitment control.

There is a LOCK TABLE statement available.


Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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