Silicon Investor (SI) -- The First Internet Community

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) -- Ignore unavailable to you. Want to Upgrade?

To: ricky who wrote (10905)	6/3/1999 12:24:00 PM
From: MeDroogies	Read Replies (1) \| Respond to of 19080

I understand it, and I'm not all that literate when it comes to techy stuff. I especially like the comments on the shorts, however. I like watching shorts die. Makes me a happy camper.

To: ricky who wrote (10905)	6/4/1999 12:43:00 AM
From: Andrew Fenic	Read Replies (1) \| Respond to of 19080

> Whereby, any/all users can access/edit the SAME record at the SAME time, and modify it. < By default Oracle 7.x implements row level locking. In practice this means that any two overlapping transactions that try to update the same row cannot both succeed. They key word there is "overlapping". Even if a record was modified by a separate transaction 10 minutes ago, your transaction may still fail if the other transaction is active. Here's a more technical link that discusses locking topics: oracle.com I couldn't find anything on Oracle's site that suggested Oracle 8i has gone beyond row locking.