Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/6925e966-26bc-8001-b158-075014259e86
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== β 3. Strict Schedules === A schedule is strict if: π No transaction can read or write a data item until the last writer commits or aborts. This means: * If Ti writes A, no other transaction can read A until Ti commits/aborts. * If Ti writes A, no other transaction can write A until Ti commits/aborts. ===== Strict = No dirty reads + No dirty writes ===== It gives the strongest form of isolation. ===== Benefit ===== * Easy to recover from crashes because you can simply undo last writer. * Most practical DBMS implement strict schedules (via strict 2PL).
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
