Templates: JPA 2.1 @ForeignKey

[deafff]

3.1.0-SNAPSHOT is still using Hibernate @ForeignKey which was deprecated after v4.3.0. I'm now getting lots of warnings and JPA validation errors (foreign keys missing in the table).

import org.hibernate.annotations.ForeignKey;

should be changed to

import javax.persistence.ForeignKey;

and annotations like

@JoinColumn(name = "COUNTRY_ID", nullable = false)
@ForeignKey(name = "FK_CITY_COUNTRY_ID")

to JPA 2.1 compliant

@JoinColumn(name = "COUNTRY_ID", nullable = false, foreignKey=@ForeignKey(name="FK_CITY_COUNTRY_ID"))

[tjuerge]

This is missing from #139.

[tjuerge]

Using the JPA annotation @ForeignKey means we have to support different JPA versions (again) in Sculptor (depending on the JPA provider):

• JPA 2.1 for Hibernate, Eclipse Link and DataNucleus
• JPA 2.0 for OpenJPA and Google AppEngine (via DataNucleus plugin)

So we have to set the JPA version in persistence.xml in accordance to the JPA provider.

[tjuerge]

It seems that the JPA 2.1 annotation @ForeignKeydoesn't work in Hibernate 4.3.x fully:

• HHH-8862 - Setting foreign key name on @CollectionTable has no effect
• Stackoverflow - The ForeignKey jpa/hibernate annotation does not work as exptected

[tjuerge]

With Hibernate 6 the deprecated annotation will be removed (HHH-8969).

[matt-hao]

hello tjuerge , i'm a freshman to learn jpa. i have also meet this problem, can u tell me how to solve this ?

[tavoda]

Because a lot changes in Hibernate 5.2 which are preparation steps for 6 we have to make at least Enum template to recognize Hibernate > 5.2 I will try to improve generation of foreign key when 5.2 is specified. First idea is to use option jpa.provider=hibernate52.

[Ysosa]

to JPA 2.1 compliant

@joincolumn(name = "COUNTRY_ID", nullable = false, foreignKey=@foreignkey(name="FK_CITY_COUNTRY_ID"))

Its work fine!! thank u