Re: ORMs comparisons/complaints.

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer,comp.lang.php

Date:

Fri, 03 Jan 2014 15:43:57 -0500

Message-ID:

<52c7210e$0$302$14726298@news.sunsite.dk>

On 1/3/2014 4:19 AM, Gordon Levi wrote:

Arne Vajh?j <arne@vajhoej.dk> wrote:

On 1/2/2014 3:34 AM, Gordon Levi wrote:

Arne Vajh?j <arne@vajhoej.dk> wrote:

Let us say that you need to add a field.

With an ORM you only need to update:
* one dataclass
* one mapping of data

With plain JDBC you need to change:
* one data class
* N SQL statements
* N places in the Java code

I don't understand this so I fear I must be doing something wrong in
my Java programs. If someone wants to add a field in a database why do
I have to alter anything in my program other than adding, for example,
getString(String columnLabel) if I want to actually use the new field
at that point in the program.

The context is that the class is persisted in a relational
database.

Thank you, it seems my fears are well founded. Does that mean that
real Java programmers go to the trouble of breaking the relational
model in order to maintain the object model?

????

If you use an object oriented language and a relational
database, then you will have both an object model and a
relational model.

Neither model need to be broken.

And it is not something special for Java.

The only thing special for Java may be that using an ORM instead
of a lot of handwritten code when moving data between the two models
is much more common than in many other languages.

Arne