CaseStudy:Designing Memento databases:Photographic equipment: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 35: | Line 35: | ||
:;Implementation: | :;Implementation: | ||
::;Intro: | ::;Intro: | ||
Revision as of 06:57, 30 April 2021
Case Study: An initial photographic equipment database
In this study, we set out to create a barebones design & implementation of a database for a photographic equipment inventory for an amateur photographer or for a solo or very small professional photographic enterprise.
Our idea is to design a barebones but extensible database that will initially consist of a single library and will be able to grow to support several interrelated, linked libraries.
Nomenclature
Before we begin, let's ensure we have an agreed understanding of the terminology we'll use in this study. In Memento, our terminology values from other Glossary#DBMS disciplines, notably relational DBMSes (or RDBMSes). The following table shows the equivalencies:
Memento | Relational | Definition |
---|---|---|
Database | Database | A generic term meaning the base of all interrelated data regarding a person or application or subject matter. |
Library | Table | Entries & fields or rows & columns of data |
Field | Column | A typed data item occupying a position within a library or table |
FieldEntry | Record (or row) | An instance or occurrence of data across fields or columns |
Entry name | Primary key | The field or ordered set of fields (Column or ordered set of columns) that identify an entry or record |
Link to entry | SQL | The means by which libraries or tables are related to each other |
- Requirements (the need)
-
- Intro
- Design considerations
- Initial camera/lens/filter&hood, flash, tripod, bag/strap
- Solution
-
- Intro
- Design
-
- Screenshots
- See the 5 email attachments
- Implementation
-
- Intro