Mixing Native SQL with Default Hibernate Behavior in an Entity Object?

Question

I'm trying to work a native sql query into an existing entity object while retaining the default Hibernate behavior for the object as a whole.

The majority of the fields on the object are mapped as so:

@Column(name = "FIRST_NAME", nullable = false)
public String getFirstName() {
    return firstName;
}

@Column(name = "MIDDLE_NAME", nullable = true)
public String getMiddleName() {
    return middleName;
}

@Column(name = "LAST_NAME", nullable = false)
public String getLastName() {
    return lastName;
}

@Column(name = "PRIMARY_EMAIL_ADDR", nullable = false)
public String getPrimaryEmailAddress() {
    return primaryEmailAddress;
}

I want to retain this functionality, but add a single field for which I need mapping to a custom (preferably native) SQL Query. I envisioned something like...

Private String foo;
@NativeSQLQuery("SELECT info FROM foo")
public String getFooInfo{return foo}

..but if there is a way to do this as simply as that, I'm missing it.

I've investigated SqlResultSetMapping and several similar Native and Named Query annotations, but all that I can find seems to presume that one is operating at the class level - that the entire entity is mapped in a custom, native fashion, not just one field. How can I go about keeping the normal functionality, but adding the custom mapping for one field? I've done this before using hbm files, I think, quite some time ago, but this current project is annotation-based. At the moment, the best I can come up with is to mark the getter @Transient and to not map it at all, but just use it to execute a query, but I'd really rather not do that, just because it seems like a total hack.

Is it really that bad to create a new entity for the data you're looking to join with? Or if you're not joining, to just simply fetch it directly from a separate entity? — dispake
– dispake, Commented Aug 15, 2013 at 18:05
That would make sense, but unfortunately in this case that's not an option. It needs to be integrated with the existing entity, but draw its value from a custom query rather than from a column. — JPittard
– JPittard, Commented Aug 15, 2013 at 18:07

Luca Basso Ricci · Accepted Answer · 2013-08-17 16:18:43Z

1

Try using a @Formula("SELECT info FROM foo"), should works

edited Aug 17, 2013 at 16:18

answered Aug 15, 2013 at 18:15

Luca Basso Ricci

18.5k2 gold badges51 silver badges75 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Mixing Native SQL with Default Hibernate Behavior in an Entity Object?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related