Hibernate Lazy loading not fully realized due to OO

Jun 2 posted in Java (RSS), comments.

Advertisements

Transfer from: http://www.sulong.info/archives/335

Object and relational database fundamental difference exists between, ORM (object / relational mapping) tried to object mapping to relational database table structure, which simplifies storage object to the database and to recover objects from the database complexity for operation database is as simple as operating targets. Hibernate ORM framework of the estimated number of the most mature, but in dealing with the inheritance relations between classes or have some problems.

Lazy look at the following code and inheritance, presentation of this mapping:

@Entity

@Table(
name =
 "a"
)

@Inheritance(
strategy =
 InheritanceType.SINGLE_TABLE
)

@DiscriminatorColumn(

                name =
 "disc"
, 
                columnDefinition =
 "varchar(4)"
, 
                discriminatorType =
 DiscriminatorType.STRING
)

public
 abstract
 class
 A {

 @Id
 private
 int
 oid;

 private
 String
 name;

}

 
@Entity

@DiscriminatorValue(
"b"
)

public
 class
 B extends
 A {

private
 String
 age;

}

 
@Entity

@DiscriminatorValue(
"c"
)

public
 class
 C extends
 B {

private
 String
 sex;

}

 
@Entity

@Table(
name =
 "d"
)

public
 class
 D {

  @Id
  private
 int
 oid;

  @ManyToOne(
fetch =
 FetchType.LAZY
)

  private
 A a;

  public
 A getA(
)
 {
return
 a}

}

When the query D class should be loaded for the Da is the delay, there is no check-off a table, naturally do not know the record why the value of the corresponding disc and do not know what kind of subclass A specific type. But check out the d object, if da! = Null da must have a value. Hibernate will generate a subclass of A, and use it as an example of da da if you really want to access the method or domain, hibernate only true to query a table. This is actually hibernate lazy loading to achieve the principle. But in this case, if you execute the following code will encounter ClassCastException,

D d =
 session.load
(
D.class
, 1
)
;

C c =
 (
C)
 d.getA
(
)
;
 // Even if  d.getA() Are you sure you are the type C  , Will  ClassCastException

hibernate generated is a subclass of A, not B or C sub-class, so when the wrong type conversion. To solve this problem, or do not use delay loading, but the performance of the above is likely to go wrong; or not to use inheritance to the following:

@Entity

@Table(
name =
 "a"
)

public
 abstract
 class
 A {

 @Id
 private
 int
 oid;

 
 private
 String
 name;

 private
 String
 age;

 private
 String
 sex;

}

 
 
@Entity

@Table(
name =
 "d"
)

public
 class
 D {

  @Id
  private
 int
 oid;

  @ManyToOne(
fetch =
 FetchType.LAZY
)

  private
 A a;

  public
 A getA(
)
 {
return
 a}

}

This effect is to limit the ability of OO; or re-check each time to change the object displayed to this:

D d =
 session.load
(
D.class
, 1
)
;

C c =
 session.load
(
C.class
, d.getA
(
)
.getOid
(
)
)
 // Back up, type specified

This is neither convenient, not OO.

It seems to want to hibernate mapping classes to maintain the characteristics of an object, or some difficulty. In many cases, these mapping classes eventually became the only responsible for mapping function in a database table objects