ORMs and Database Design
2024
- 105Usage
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Usage105
- Downloads80
- Abstract Views25
Thesis / Dissertation Description
This thesis explores the relationship between database design and Object-Relational Mapping (ORM) design, investigating how they have evolved together and influenced each other. It addresses a theoretical discussion, a practical implementation, and some observations regarding integrating an ORM into my Senior Design project. My Senior Design project was originally built without the intention of implementing an ORM.There are a lot of complicated discrepancies between Relational Databases (RDBs) and Object-Oriented Programming Languages (OOPLs), called the Impedance Mismatch Problem. The fact that they are both foundational pillars in software engineering means that one cannot simply change to match the other. ORMs were developed in order to reconcile the differences between the two paradigms so that each and every individual developer does not have to tackle the problem on their own.Mapping data from OOPLs to RDBs and back again is non-trivial and requires trade-offs in design considerations. That is why a variety of ORMs have popped up: to provide options to developers in terms of support and applicability. This thesis explores some of these trade-offs, especially as they relate to different ORM design patterns.Key Words: ORM, Object-Relational Mapping, RDB, Relational Database, Object-Oriented Programming, Impedance Mismatch Problem
Bibliographic Details
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know