Re: ORM or JDBC?
Michal Kleczek wrote:
What ORM does (or shoud do) is it translates one representation of data (a
ResultSet) into another (user defined).
The problem is that existing ORMs fail to do it for arbitrary chosen class
models. Instead they force a programmer to define _another_ class model that
is suited for this particular ORM.
Some would call it "accidental complexity". Others: "tail wags the dog".
I would call that "misinformation". ORMs can turn any data model into any
object model that you can do with JDBC.
Why do people keep making these false statements "JPA cannot do X"? It's very
irresponsible to give people such false information, even unethical.
Lew said:
, and that's what you will have to do by hand if
not with a framework.
Michal Kleczek wrote:
I have to do it by hand anyway because I have to translate the data from one
representation (a ResultSet) to another (a Widget or it's subclass or in
But you have to do it with more code and tanglement with raw JDBC generally
than with the boilerplate-saving and neatly-separated way that JPA does.
There is a difference. The JPA approach, properly applied, reduces effort and
risk involved in mapping a data store to your object model.
case of Swing to JComponent or its subclass).
I cannot see how existing ORMs (JPA included) can help me with this.
Too bad for you, then.
--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg