Home / Questions / 359396
Accepted
Alan Rodríguez
Asked: 2020-05-27 01:32:15 +0800 CST 2020-05-27 01:32:15 +0800 CST

Is it possible to define a policy for naming constraints in Spring JPA?

  • 772

I know that it is possible to name them Foreing Keysand also manually define the constraints, but isn't there a way to define a naming policy for each type of constraint and thus avoid the random identifiers that Spring generates by default?

eg for a constraint of typeUNIQUE, Spring generates the following name:UK_ob8kqyqqgmefl0aco34akdtpebut I don't know if it is possible to somehow define the following pattern:AK_TABLE_ATTRIBUTEso that Spring uses it every time it generates that type of constraint.

The foregoing more than anything to standardize the restrictions and facilitate their maintenance.

spring

1 Answers

  1. Best Answer

    As you comment, there is @javax.persistence.ForeignKey:

    @OneToOne()
@JoinColumn(name="vehicle_id", referencedColumnName="vehicleId", foreignKey=@ForeignKey(name = "Fk_userdetails_vehicle"))
public Vehicle getVehicle() {
    return vehicle;
}

    But if you want to change the naming strategy in general, I found this: org.springframework.boot.orm.jpa.hibernate.SpringImplicitNamingStrategy

    This class allows you to define the name of the elements of your database, from the name of the tables, columns to the foreign keys. It's really an extension of the hibernate implementation :

    • 2