root/logseq_notes
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Auto saved by Logseq

Browse source
This commit is contained in:
Ryan 2023-06-14 19:25:45 +08:00
parent c664211fe8
commit 86db38df5b
1 changed files with 16 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

35
pages/总复习2023t1.md
View file

@ -1005,25 +1005,21 @@
- The instances of a potential subclass participate in a relationship unique to that subclass.
- DONE Block 3
- DONE DB transaction management
- DONE anomalies
:LOGBOOK:
CLOCK: [2023-06-14 Wed 16:41:52]--[2023-06-14 Wed 16:49:14] => 00:07:22
:END:
- DONE Deadlock and how it can be resolved. #flashcard
id:: 64841da4-d8ce-46f5-bbe6-4dee620cde75
- A deadlock is a situation in which two or more transactions are unable
to proceed because each is waiting for a resource held by the other,
resulting in a circular dependency and a system halt. It is a form of
resource contention that can occur in concurrent systems, including
database management systems.
- Example:
- Cascading rollback #flashcard
id:: 64897f0b-dda6-4cc3-a9c3-cf630bcb0658
- Cascading Rollback: a transaction (T1) causes a
failure and a rollback must be performed. Other
transactions dependent on T1's actions must also
be rollbacked, thus causing a cascading effect.
- One transaction's failure causes many to fail.
- DONE Deadlock and how it can be resolved. #flashcard
id:: 64841da4-d8ce-46f5-bbe6-4dee620cde75
- A deadlock is a situation in which two or more transactions are unable
to proceed because each is waiting for a resource held by the other,
resulting in a circular dependency and a system halt. It is a form of
resource contention that can occur in concurrent systems, including
database management systems.
- Example:
- Cascading rollback #flashcard
id:: 64897f0b-dda6-4cc3-a9c3-cf630bcb0658
- Cascading Rollback: a transaction (T1) causes a
failure and a rollback must be performed. Other
transactions dependent on T1's actions must also
be rollbacked, thus causing a cascading effect.
- One transaction's failure causes many to fail.
- DONE ACID (Atomicity, Consistency, Isolation, Durability): A set of properties that guarantee the reliability and integrity of database transactions. #flashcard
id:: 64841da4-0055-4d34-9f61-1402ff068ec7
collapsed:: true
@ -1102,6 +1098,7 @@
id:: 64842000-c15a-4b8f-95c3-d6c6e49e4af0
- Fourth Normal Form (4NF): 4NF is a further refinement of BCNF that ensures that _a table does not contain any multi-valued dependencies._
- Fifth Normal Form (5NF): 5NF is the highest level of normalization and involves decomposing a table into smaller tables to _remove data redundancy and improve data integrity._
- Anomaly
- LATER Block 4
- DONE Distributed DBMS
- DONE client server arch #flashcard