My article on
O/R mapping in dynamic languages has been published by ACM Queue magazine. The article looks at how Grails O/R mapping (GORM) works. It compares and contrasts GORM with Hibernate, focusing on three areas: defining object-relational mapping; performing basic save, load, and delete operations on persistent objects; and executing queries. The article describes how GORM leverages the dynamic features of Groovy to provide a different flavor of O/R mapping. It discusses the benefits and the drawbacks of using GORM. I look forward to getting your feedback.
tags: dynamic java or orm mapping grails metaobject hibernate groovy languages persistence
links: digg this del.icio.us technorati reddit