JPA @JoinColumn issues while joining on non primary key columns

Question

I want to connect table based on one direction join, here is my code:

Class Person {

@id
String person_sk;

int person_id;

String Person_name;

@OneToMany
@joinColumn (name="person_reference_id")
List<address> getAddresses() {}

}

class Address
{

@id
int person_reference_id (referred from Person);

@id
int address_id;

@id
int phone_id;

String street_name, zip_code;

}

Now when I do getAddress, it does not work, because my join is based on person_ref_id and @id (primaryKey) column in Person class is person_sk.

If I use referencedColumn then also it doesn't work.

score 0 · Answer 1 · edited May 23 '17 at 10:34

0

How can I make this work??

Normalize your database to use common PK-FK relationships. If needed - define composite PK.

edited May 23 '17 at 10:34

Community

1
1

answered Jul 09 '12 at 08:45

d1e

6,372
2
28
41

well thats correct, but its really strange why framework is abandoning you to implement such odd situation. – Bhumir Jhaveri Jul 09 '12 at 23:25
1

All this is good when it's ideal scenario, but everytime one dont end up in getting ideal scenario and there are hardly any changes that can be applied to the data model. – Bhumir Jhaveri Jul 09 '12 at 23:27
I think it is good they do not support such ridiculous stuff. It is just that if they were to workaround every feature concerning other layers, it would be over-engineered. Here is a workaround you can try http://stackoverflow.com/a/1506775/685962 – d1e Jul 10 '12 at 06:50
9

Telling someone to normalize their database does not work when you have legacy databases that actually pre-date Hibernate and contain millions upon millions of records and 15 years of legacy business logic running on dozens of servers. – cbmeeks Aug 31 '15 at 21:27
this is useless advice if you can't change your data model ffs – Enerccio Nov 11 '22 at 13:02
Did you manage to resolve the problem? – d1e Nov 30 '22 at 07:17

score 0 · Answer 2 · answered May 05 '23 at 14:58

You should use right @Id annotation on the joined Entity(table) property(column), which you want to join by. The best solution is to normalize the tables in the DB, and make the appropriate changes in your Entities.

@Data
@Entity
@Table(name = "person")
class Person {

    @Id
    String person_sk;

    int person_id;

    String Person_name;

    @OneToMany(cascade = CascadeType.ALL)
    @JoinColumn(name = "person_sk")
    List<address> getAddresses() {}
}

@Data
@Entity
@Table(name = "address")
class Address {

    @Id
    int person_reference_id;

    int address_id;

    int phone_id;

    String street_name, zip_code;
}

score -2 · Answer 3 · answered Jul 09 '12 at 12:58

-2

Unusual data model, you may want to rethink it.

Also, normally it is best to define a @OneToMany using a mappedBy and an inverse @ManyToOne.

JPA does not directly support your data model, but if you are using EclipseLink, you can define the OneToManyMapping using a DescriptorCustomizer and use whatever foreign keys or join conditions you require.

answered Jul 09 '12 at 12:58

James

17,965
11
91
146

its true, but this cant be modified since its coming from certain external apps, but this is not appropriate functionality supported by jpa framework – Bhumir Jhaveri Jul 09 '12 at 23:26

JPA @JoinColumn issues while joining on non primary key columns

3 Answers3

Linked