Gorilla and King Portfolio Candidates 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.

Strategies & Market Trends : Gorilla and King Portfolio Candidates

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: emmeling who wrote (15066)	1/13/2000 3:28:00 PM
From: Thomas Mercer-Hursh	Read Replies (1) of 54805

agree with you about row-level locking. It was a major problem and Oracle solved it. THEN, once applications were programmed to use Oracle's method of row-level locking, it wasn't easy to switch to anyone else's implementation. I don't follow you here. Regardless of how the database implements it, one requests the lock on the record. If the database turns this into a page-lock, it can produce contention problems impacting scalability or, if the programmer is sensitive to this, it may distort the schema design to force record per page or what-have-you. But, the program doesn't know.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next