Comments on: Episode 55: Object-Relational Mapping http://faceoffshow.com/2010/02/09/episode-55-object-relational-mapping/ Your face-to-face web technology podcast Thu, 15 Jan 2015 09:15:47 +0000 hourly 1 http://wordpress.org/?v=3.7.1 By: Brian http://faceoffshow.com/2010/02/09/episode-55-object-relational-mapping/comment-page-1/#comment-1082 Sat, 27 Feb 2010 18:25:30 +0000 http://faceoffshow.com/?p=772#comment-1082 Exactly. We use Seam Framework and this is the preferred approach. Once the database is in place we run a generator that looks at the database and creates all of the entities, wiring, and views. It is much like scaffolding in Rails. You have a working CRUD app at this point to work with.

]]> By: Jade Robbins http://faceoffshow.com/2010/02/09/episode-55-object-relational-mapping/comment-page-1/#comment-1081 Sat, 27 Feb 2010 16:46:31 +0000 http://faceoffshow.com/?p=772#comment-1081 So you design the database, then wrap the ORM around it. That is a good way to keep your databases optimized and sane. I didn’t really think about that :D

]]> By: Brian http://faceoffshow.com/2010/02/09/episode-55-object-relational-mapping/comment-page-1/#comment-1078 Sat, 27 Feb 2010 15:29:07 +0000 http://faceoffshow.com/?p=772#comment-1078 We use ORMs for every new project. The pros far outweigh the cons. We use a bottom up approach so we design the database first. The only time I wouldn’t possibly use one is when working with a legacy database. There are a lot of poorly designed databases out there.

Two more ORMs.

Java – Hibernate
.Net – nHibernate

]]>