Comments on: Episode 55: Object-Relational Mapping

By: Brian

Sat, 27 Feb 2010 18:25:30 +0000

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

Sat, 27 Feb 2010 16:46:31 +0000

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

]]>

By: Brian

Sat, 27 Feb 2010 15:29:07 +0000

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

]]>