{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:33:44Z","timestamp":1750307624996,"version":"3.41.0"},"reference-count":3,"publisher":"Association for Computing Machinery (ACM)","issue":"3","license":[{"start":{"date-parts":[[2008,5,1]],"date-time":"2008-05-01T00:00:00Z","timestamp":1209600000000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2008,5]]},"abstract":"<jats:p>In the early 1990s, when object-oriented languages emerged into the mainstream of software development, a noticeable surge in productivity occurred as developers saw new and better ways to create software programs. Although the new and efficient object programming paradigm was hailed and accepted by a growing number of organizations, relational database management systems remained the preferred technology for managing enterprise data. Thus was born ORM (object-relational mapping), out of necessity, and the complex challenge of saving the persistent state of an object environment in a relational database subsequently became known as the object-relational impedance mismatch.<\/jats:p>","DOI":"10.1145\/1394127.1394141","type":"journal-article","created":{"date-parts":[[2008,7,29]],"date-time":"2008-07-29T13:22:19Z","timestamp":1217337739000},"page":"38-47","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":6,"title":["Exposing the ORM Cache"],"prefix":"10.1145","volume":"6","author":[{"given":"Michael","family":"Keith","sequence":"first","affiliation":[{"name":"Oracle"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Randy","family":"Stafford","sequence":"additional","affiliation":[{"name":"Oracle"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2008,5]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"publisher","DOI":"10.1109\/NWESP.2005.60"},{"volume-title":"Patterns of Enterprise Application Architecture","author":"Fowler M.","key":"e_1_2_1_2_1","unstructured":"Fowler , M. 2004. Patterns of Enterprise Application Architecture . Addison-Wesley . Fowler, M. 2004. Patterns of Enterprise Application Architecture. Addison-Wesley."},{"volume-title":"Pro EJB 3: Java Persistence API","author":"Keith M.","key":"e_1_2_1_3_1","unstructured":"Keith , M. , Schincariol , M. 2006. Pro EJB 3: Java Persistence API . Apress . Keith, M., Schincariol, M. 2006. Pro EJB 3: Java Persistence API. Apress."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1394127.1394141","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1394127.1394141","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T12:45:53Z","timestamp":1750250753000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1394127.1394141"}},"subtitle":["Familiarity with ORM caching issues can help prevent performance problems and bugs."],"short-title":[],"issued":{"date-parts":[[2008,5]]},"references-count":3,"journal-issue":{"issue":"3","published-print":{"date-parts":[[2008,5]]}},"alternative-id":["10.1145\/1394127.1394141"],"URL":"https:\/\/doi.org\/10.1145\/1394127.1394141","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2008,5]]},"assertion":[{"value":"2008-05-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}