Auto saved by Logseq
This commit is contained in:
parent
4f5f7ea96f
commit
a85955a555
|
@ -1004,8 +1004,7 @@
|
|||
id:: 6489683b-7d47-4246-afdf-83fdb35a00f6
|
||||
- There are attributes that apply to some (but not all) instances of an entity.
|
||||
- The instances of a potential subclass participate in a relationship unique to that subclass.
|
||||
- LATER SQL
|
||||
- LATER Designing databases
|
||||
- DONE Designing databases
|
||||
- Understand Database Design Methodology #flashcard
|
||||
- Conceptual database design
|
||||
- The process of constructing a model of the data used in an enterprise, independent of all physical considerations.
|
||||
|
@ -1013,11 +1012,13 @@
|
|||
- Maps the conceptual data model on to a logical model (e.g. relational), but independent of a particular DBMS and other physical considerations.
|
||||
- Physical database design
|
||||
- The process of producing a description of the implementation of the database (tailored to specific DBMS);
|
||||
- general steps for Database Design Methodology.
|
||||
- general steps for Database Design Methodology. #flashcard
|
||||
- Gather requirements
|
||||
- Conceptual database design
|
||||
- Logical database design
|
||||
- Physical database design
|
||||
- LATER SQL
|
||||
- purpose and importance of SQL.
|
||||
- DONE Block 3
|
||||
collapsed:: true
|
||||
- DONE DB transaction management
|
||||
|
|
Loading…
Reference in a new issue