Wikipedia

Object–relational mapping: Difference between revisions

Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
I added a link to heap https://en.wikipedia.org/wiki/Heap_(data_structure)
Both previous links lead to 404's/not-founds. I believe this is what the original author was intending to reference
Line 44:
 
==Comparison with traditional data access techniques==
Compared to traditional techniques of exchange between an object-oriented language and a relational database, ORM often reduces the amount of code that needs to be written.<ref>Douglas Barry, Torsten Stanienda, "Solving the Java Object Storage Problem," Computer, vol. 31, no. 11, pp. 33-40, Nov. 1998, [httphttps://www2www.computer.org/portal/web/csdl/doimagazine/10.1109co/2.730734 http:1998/11/www2.computer.orgry033/portal/web/csdl/doi/10.1109/2.730734 ], Excerpt at http://www.service-architecture.com/object-relational-mapping/articles/transparent_persistence_vs_jdbc_call-level_interface.html13rRUxC0SRY. Lines of code using O/R are only a fraction of those needed for a call-level interface (1:4). ''For this exercise, 496 lines of code were needed using the ODMG Java Binding compared to 1,923 lines of code using JDBC.''</ref>
 
Disadvantages of ORM tools generally stem from the high level of [[Database abstraction layer|abstraction]] obscuring what is actually happening in the implementation code. Also, heavy reliance on ORM software has been cited as a major factor in producing poorly designed databases.<ref>Josh Berkus, "Wrecking Your Database", Computer, Aug. 2009, https://www.toolbox.com/tech/data-management/blogs/wrecking-your-database-080509/</ref>
Retrieved from "https://en.wikipedia.org/wiki/Object–relational_mapping"