Poka-yoke is a Japanese term for a process that is translated in English as "mistake proofing." Various poka-yoke tools and techniques establish a better baseline for error-free processes. The concept of poka-yoke involves limiting the number of possible incorrect options, resulting in fewer (or no) user errors.
The problems caused by concurrency are even more important than the ability to support concurrent transactions. For example, when one user is changing data but has not yet saved (committed) that data, then the database should not allow other users who query the same data to view the changed, unsaved data. Instead the user should only view the original data.
Almost all databases deal with concurrency the same way, although the terminology may differ. The general principle is that changed but unsaved data is held in some sort of temporary log or file. Once it is saved, it is then written to the database’s physical storage in place of the original data. As long as the user performing the change has not saved the data, only he should be able to view the data he is changing. All other users querying for the same data should view the data that existed prior to the change. Once the user saves the data, new queries should reveal the new value of the data.
Read More »
Join 138,000+ IT pros on our weekly newsletter
Home | Advertising Info | Write for Us | About | Contact Us
2010 - 2015
Partner Sites :