【问题标题】:How to define the order of fields on foreign key mapping using Hibernate and JPA?如何使用 Hibernate 和 JPA 定义外键映射的字段顺序?
【发布时间】:2017-06-03 08:48:27
【问题描述】:

我在 hibernate 部署我的应用程序时遇到了一些问题。

我在日志中看到一些错误,说 hibernate 无法更新表,因为发现外键违规,如下所示:

Caused by: org.postgresql.util.PSQLException: ERROR: insert or update on table "order" violates foreign key constraint "fk1w50d63tw42cwgrb7pjn11crs"
  Detail: Key (id_office_o, id_period)=(2, 1) is not present in table "office".

但在我的表定义中,我将 FK fk_order_office_o 作为 (id_period, id_office_o) 关系。

这是我的表格定义。

CREATE TABLE period (
    id_period INTEGER PRIMARY KEY NOT NULL,
    initial_date TIMESTAMP,
    final_date TIMESTAMP
);

CREATE TABLE office (
    id_period INTEGER NOT NULL,
    id_office INTEGER NOT NULL,
    large_name VARCHAR(50) NOT NULL,
    code_name VARCHAR(2) NOT NULL,
    CONSTRAINT pk_office PRIMARY KEY (id_periodo, id_office),
    CONSTRAINT fk_office_period FOREIGN KEY (id_period) REFERENCES period (id_period)
);
CREATE UNIQUE INDEX uk_office_id_office ON office (id_office);

CREATE TABLE order (
    id_order INTEGER PRIMARY KEY NOT NULL,
    id_period INTEGER,
    id_office_o INTEGER,
    id_office_d INTEGER,
    status INTEGER,
    CONSTRAINT fk_order_office_o 
        FOREIGN KEY (id_period, id_office_o) 
        REFERENCES office (id_period, id_office) 
        MATCH SIMPLE ON UPDATE CASCADE ON DELETE RESTRICT,
    CONSTRAINT fk_order_office_d
        FOREIGN KEY (id_period, id_office_d) 
        REFERENCES office (id_period, id_office),
        MATCH SIMPLE ON UPDATE CASCADE ON DELETE RESTRICT,
    CONSTRAINT fk_order_period
        FOREIGN KEY (id_period)
        REFERENCES period (id_period)
        MATCH SIMPLE ON UPDATE CASCADE ON DELETE RESTRICT
);

这些是我表格上的数据。

Period.
+------------+--------------+------------+
| id_period  | initial_date | final_date |
|------------|--------------|------------+
| 1          | 2016-01-01   | 2017-12-31 |
+------------+--------------+------------+

Office.
+------------+-----------+------------+-----------+
| id_period  | id_office | large_name | code_name |
|------------|-----------|------------|-----------|
| 1          | 1         | Sales      | SL        |
| 1          | 2         | Billing    | BL        |
| 1          | 3         | Shipments  | SH        |
| 1          | 4         | Returns    | RT        |
+------------+-----------+------------+-----------+

Order.
+------------+-----------+--------------+--------------+-----------+
| id_order   | id_period | id_office_o  | id_office_d  | status    |
+------------+-----------+--------------+--------------+-----------+
| 1          | 1         | 2            | 3            | 1         |
| 2          | 1         | 2            | 3            | 1         |
| 1          | 1         | 3            | 4            | 1         |
| 1          | 1         | 1            | 2            | 1         |
+------------+-----------+--------------+--------------+-----------+

如您所见,与订单表相关的office 表的FK 有一个名为fk_order_office_o 的CONSTRAINT,它使用id_period 和id_office,按此顺序。

实体映射在这里:

@Embeddable
public class OfficePK implements Serializable {

    @Column(name = "id_period")
    private Integer idPeriod;

    @Column(name="id_office")
    private Integer idOffice;

    public OfficePK() {
    }

    public OfficePK(Integer idPeriod, Integer idOffice) {
        this.idPeriod = idPeriod;
        this.idOffice = idOffice;
    }

    ... 

}


@Entity
@Table(schema="enterprise", name="office")
public class Office {


    @EmbeddedId
    private OfficePK idOffice;

    private String largeName;
    private String codeName;

    public Office() {
    }

    public OfficePK getIdOffice() {
        return this.idOffice;
    }

    public void setIdOffice(OfficePK idOffice) {
        this.idOffice = idOffice;
    }

    ...

}


@Entity
@Table(schema="operation", name = "order")
public class Order {

    @Column(name="id_order")
    private Integer idOrder;

    @ManyToOne
    @JoinColumns(
        value = {
            @JoinColumn(name="id_period", 
                        referencedColumnName = "id_period", 
                        nullable = false, insertable = false, 
                        updatable = false),
            @JoinColumn(name="id_office_o",  
                        referencedColumnName = "id_office",
                        nullable = false, insertable = false, 
                        updatable = false)
        },
        foreignKey = @ForeignKey(name = "fk_order_office_o")
    )
    private Office officeO;

    @ManyToOne
    @JoinColumns(
        value = {
            @JoinColumn(name="id_period", 
                        referencedColumnName = "id_period", 
                        nullable = false, insertable = false, 
                        updatable = false),
            @JoinColumn(name="id_office_d",  
                        referencedColumnName = "id_office",
                        nullable = false, insertable = false, 
                        updatable = false)
        },
        foreignKey = @ForeignKey(name = "fk_order_office_d")
    )
    private Office officeD;

    public Order() {
    }

    ...

}

在部署应用程序时,我看到一些引起我注意的错误:

  1. 我没有按照日志文件中显示的顺序定义外键,日志文件正在寻找(id_office_o, id_period) 的对,但外键在表和映射中定义为(id_period, id_office_o)。
  2. 我正在设置外键的名称,但是休眠正在设置一个随机名称,例如fk1w50d63tw42cwgrb7pjn11crs

如何定义实体的外键映射上的字段顺序?,可以吗?..或者应该如何定义或映射外键的字段?

我正在使用

  1. 休眠 5.2.6.Final
  2. Spring-JPA 1.10.6.RELEASE

谢谢大家。

【问题讨论】:

  • @ManyToOne @JoinColumn(name = "id_period") private Integer idPeriod; ManyToOne 注解不能用于 Integer
  • 是的,我抄写错了,我已经更正了,谢谢@MdZahidRaza

标签: java spring hibernate jpa hibernate-mapping


【解决方案1】:

与@ForeignKey名称相关的部分可能与HHH-11180相关。

关于外键顺序的部分,你可以通过提供一个自定义的org.hibernate.boot.model.naming.ImplicitNamingStrategy实现来解决它,它从默认的org.hibernate.boot.model.naming.ImplicitNamingStrategyJpaCompliantImpl扩展并覆盖determineForeignKeyName方法,以便它生成带有列的外键您需要的订单。

现在,您所经历的所有这些努力都是您没有正确管理架构的味道。您永远不应该在生产中使用自动 HBM2DDL 模式生成。 You should use Flyway instead。这是您环境中的根本问题。

【讨论】:

  • 感谢@vlad-mihalcea,我在none 的hbm2ddl 设置中为FK 名称和生产环境实现ImplicitNamingStrategy。
猜你喜欢
  • 1970-01-01
  • 1970-01-01
  • 2011-03-20
  • 1970-01-01
  • 2023-04-03
  • 2020-06-25
  • 2021-12-12
  • 2014-10-12
  • 1970-01-01
相关资源
最近更新 更多