views:

41

answers:

3

I am developing a project in which I am persisting some POJOs by adding Hibernate annotations. One problem I am running into is that code like this fails, as Hibernate tries to map the sub-fields within the Time_T onto the same column (i.e. startTime.sec and stopTime.sec both try to map to the colum sec, causing an error).

@Entity
public class ExampleClass
{
  @Id
  long eventId;

  Time_T startTime;
  Time_T stopTime;
}

@Embeddable
public class Time_T
{
  int sec;
  int nsec;
}

As there will be many occurrences like this throughout the system, it would be nice if there was an option to automatically append a prefix to the column name (e.g. make the columns be startTime_sec, startTime_nsec, stopTime_sec, stopTime_nsec), without having to apply overrides on a per-field basis. Does Hibernate have this capability, or is there any other reasonable work-around?

A: 

Probably following thread have the answer:

http://stackoverflow.com/questions/331744/jpa-multiple-embedded-fields

Tahir Akhtar
+2  A: 

Try setting the property hibernate.ejb.naming_strategy to org.hibernate.cfg.DefaultComponentSafeNamingStrategy

Bozho
Exactly what I needed. Thanks.
VeeArr
A: 

Another way to solve the problem is by using @AttributeOverrides and @AttributeOverride annotations. In your example the Time_T.sec property is mapped to sec column. You could map ExampleClass like this:

@Entity
public class ExampleClass {
    @Id
    long eventId;

    @AttributeOverrides(
        @AttributeOverride(name = "sec", column = @Column(name = "start_sec"))
    )
    Time_T startTime;
    Time_T stopTime;
}

The result mapping is startTime.sec <=> start_sec and stopTime.sec <=> sec. Of course you could use annotations to create a more meaningful name for stopTipe.sec column.

matheus.emm
This is explicitly what I don't want to do, as there could be many instances of this pattern throughout the code. I would not want to add in the `@AttributeOverrides` annotations several hundred times.
VeeArr
I'm sorry, I didn't pay enough attention to your first message. You clearly stated that you didn't want to manually override the fields.
matheus.emm