Oracle Corporation (ORCL) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Oracle Corporation (ORCL)

ORCL 169.01

-2.2%

Jan 29 3:59 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Andrew Fenic who wrote (10908)	6/4/1999 10:33:00 AM
From: Michael Olin	Read Replies (1) of 19080

Whereby, any/all users can access/edit the SAME record at the SAME time, and modify it. It really depends on how you are accessing the records. It is quite possible, for example, for two users running an Oracle Forms application to make non-conflicting updates to the same record and have both transactions succeed. Again, it depends on exactly what is being done and how the application is written. As a general rule however, the first user to lock the record gets to make changes and other users must wait until a commit (save) to modify the same record. If other users were already looking at the un-changed record in Oracle Forms, for example (and waiting to lock it), they will be notified that the record has been changed by another user and required to re-query the database before making any changes. The same holds for any other method of accessing the database where the second user's transaction is in progress when the first user commits. The other topic to look up for more technical information is "read-consistency" -Michael

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next