Skip site navigation (1) Skip section navigation (2)

Re: Non-ORM layers over JDBC

From: Tore Halset <halset(at)pvv(dot)ntnu(dot)no>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Non-ORM layers over JDBC
Date: 2008-03-26 10:21:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc

On Mar 24, 2008, at 6:45 , Craig Ringer wrote:
> I'm fairly new to Java (sorry!) and struggling with the database  
> access area.

A newbie should not question if he should use a ORM, but instead focus  
on which ORM to use. Please spend some time finding a good ORM that  
you feel comfortable with.

Why you should use an ORM:
  * Less boring code to write when bringing over data from PostgreSQL  
to your java application and back.
  * Simpler refactoring. What if you want to change the primary key,  
add a relationship or whatever.
  * Easier to support several databases. Thanks to Apache Cayenne, my  
app work with PostgreSQL, MS SQL Server and Derby and others.
  * And lots of other good reasons you will discover.

When to not use an ORM:
  * Some specially tuned reporting queries

> What do people here use? Just use the JDBC directly? Use an ORM  
> layer even though you just target PostgreSQL and work around its  
> limitations and quirks? Use a different ORM layer without weird  
> limitations and quirks? Some other tool I haven't been able to find  
> out about?

I am using Apache Cayenne. It is a simple and elegant ORM with a swing  
modeler tool that helps you create the mapping.

  - Tore.

In response to


pgsql-jdbc by date

Next:From: Woody WoodringDate: 2008-03-26 12:53:32
Subject: Advice fetching Array data with JDBC 8.3 driver
Previous:From: Joao Rui LealDate: 2008-03-26 10:19:38
Subject: Re: Deadlock while using getNotifications() and Statement.executeQuery()

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group