使用Hibernate的Spring Boot在启动时使用H2数据库生成丢弃约束错误

Question

我正在使用spring-boot并且配置了H2数据库(在application.properties中).

spring.datasource.url=jdbc:h2:mem:AZ;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE
spring.datasource.driverClassName=org.h2.Driver
spring.datasource.username=sa
spring.datasource.password=
spring.jpa.database-platform=org.hibernate.dialect.H2Dialect

在日志中,我看到以下错误:

o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [
        name: default
        ...]
org.hibernate.Version                    : HHH000412: Hibernate Core {4.3.5.Final}
org.hibernate.cfg.Environment            : HHH000206: hibernate.properties not found
org.hibernate.cfg.Environment            : HHH000021: Bytecode provider name : javassist
o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {4.0.4.Final}
org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
o.h.h.i.ast.ASTQueryTranslatorFactory    : HHH000397: Using ASTQueryTranslatorFactory
org.hibernate.tool.hbm2ddl.SchemaExport  : HHH000227: Running hbm2ddl schema export
org.hibernate.tool.hbm2ddl.SchemaExport  : HHH000389: Unsuccessful: alter table key_request drop constraint FK_53shrbc21c25inskpp1yoxxss if exists
org.hibernate.tool.hbm2ddl.SchemaExport  : Table "KEY_REQUEST" not found; SQL statement:
    alter table key_request drop constraint FK_53shrbc21c25inskpp1yoxxss if exists [42102-178]

即使hibernate将这些报告为错误,我也可以登录到H2控制台并查看约束,它们看起来很好.

SELECT TABLE_NAME, INDEX_NAME, COLUMN_NAME, INDEX_TYPE_NAME FROM information_schema.indexes WHERE TABLE_NAME='KEY_REQUEST';
TABLE_NAME    INDEX_NAME                            COLUMN_NAME  INDEX_TYPE_NAME  
KEY_REQUEST   PRIMARY_KEY_F                         REQUEST_ID   PRIMARY KEY
KEY_REQUEST   FK_53SHRBC21C25INSKPP1YOXXSS_INDEX_F  USER_ID      INDEX

如果真的看起来hibernate试图在实际创建数据库之前删除这些约束(即在休眠中出现某种错误).有没有办法避免这些错误堵塞日志或在某处表明真正的故障？

更新1

尝试强制应用程序仅使用此设置执行更新:

spring.jpa.hibernate.ddl-auto=update

导致以下错误(所有其他错误消失):

org.hibernate.tool.hbm2ddl.SchemaUpdate  : HHH000388: Unsuccessful: alter table lti_result add constraint FK_1cnh9amy5br8owkmafsrth3as foreign key (result_id) references lti_link
org.hibernate.tool.hbm2ddl.SchemaUpdate  : Constraint "FK_1CNH9AMY5BR8OWKMAFSRTH3AS" already exists; SQL statement: 
    alter table lti_result add constraint FK_1cnh9amy5br8owkmafsrth3as foreign key (result_id) references lti_link [90045-178]

注意:源代码在这里:https://github.com/azeckoski/lti_starter

特别是配置:https: //github.com/azeckoski/lti_starter/blob/master/src/main/resources/application.properties

和模型:https: //github.com/azeckoski/lti_starter/tree/master/src/main/java/ltistarter/model

Answer 1

因为您使用的是内存数据库,所以Hibernate在执行时不会找到任何表:

hibernate.hbm2ddl.auto=create-drop

那是因为语句顺序是:

• 放弃约束(fk)
• 放下桌子
• 创建表格

• 创建约束(fk)

  Query:{[alter table tableIdentifier drop constraint FK_202gbutq8qbxk0chvcpjsv6vn][]} 
  ERROR [main]: o.h.t.h.SchemaExport - HHH000389: Unsuccessful: alter table tableIdentifier drop constraint FK_202gbutq8qbxk0chvcpjsv6vn
  ERROR [main]: o.h.t.h.SchemaExport - user lacks privilege or object not found: PUBLIC.TABLEIDENTIFIER
  Query:{[drop table sequenceIdentifier if exists][]} 
  Query:{[drop table tableIdentifier if exists][]} 
  Query:{[create table sequenceIdentifier (id bigint not null, primary key (id))][]} 
  Query:{[create table tableIdentifier (id bigint not null, sequenceIdentifier_id bigint, primary key (id))][]} 
  Query:{[alter table tableIdentifier add constraint FK_202gbutq8qbxk0chvcpjsv6vn foreign key (sequenceIdentifier_id) references sequenceIdentifier][]} 
  Query:{[create sequence hibernate_sequence start with 1 increment by 1][]} 
  

您可以通过更改hibernate.hbm2ddl.auto来更新:

hibernate.hbm2ddl.auto=update

Answer 2

尝试create-only：

spring.jpa.properties.hibernate.hbm2ddl.auto=create-only

它至少从 5.2（甚至更早）开始被添加到 Hibernate 中，我没有找到任何合适的文档，但它提到了用户指南：23.15。自动模式生成

此外，如果您在日志中看到：

WARN  SessionFactoryOptionsBuilder:394 - Unrecognized hbm2ddl_auto value : create-only.  Supported values include 'create', 'create-drop', 'update', 'none' and 'validate'.  Ignoring

这可能是一个误报，实际上它是有效的