在启动时执行 DDL 验证时不使用@TableHibernate。使用飞行通道和测试容器

Question

我对Hibernate有问题。我正在通过Flyway迁移创建表。下面显示了初始迁移脚本的一部分片段。该脚本确实运行（我可以在DEBUG模式下看到它）。

脚本运行后，Hibernate的验证器似乎没有使用我通过< code>javax.persistence提供的实体的表名。

为了清楚起见，这里有一些省略的实体：

import javax.persistence.*;


@Entity
@Table(name = "IngredientCategories")
public class IngredientCategory implements IEntity {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private long id;

    @Column(nullable = false, length = 128)
    private String name;

    ...
}

CREATE TABLE `IngredientCategories` (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `description` varchar(255) DEFAULT NULL,
  `name` varchar(128) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;

查看日志，Flyway迁移正在运行，然后我收到Hibernate验证错误。

2020-10-24 11:22:11.952 DEBUG 91583 --- [           main] o.f.core.internal.command.DbMigrate      : Successfully completed migration of schema `test` to version 1 - init
2020-10-24 11:22:11.961 DEBUG 91583 --- [           main] o.f.c.i.s.JdbcTableSchemaHistory         : Schema History table `test`.`flyway_schema_history` successfully updated to reflect changes
2020-10-24 11:22:11.970  INFO 91583 --- [           main] o.f.core.internal.command.DbMigrate      : Successfully applied 1 migration to schema `test` (execution time 00:00.107s)
2020-10-24 11:22:11.972 DEBUG 91583 --- [           main] org.flywaydb.core.Flyway                 : Memory usage: 82 of 354M
2020-10-24 11:22:12.088  INFO 91583 --- [           main] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
2020-10-24 11:22:12.125  INFO 91583 --- [           main] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.4.20.Final
2020-10-24 11:22:12.237  INFO 91583 --- [           main] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
2020-10-24 11:22:12.350  INFO 91583 --- [           main] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
2020-10-24 11:22:12.998  WARN 91583 --- [           main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [ingredient_categories]
2020-10-24 11:22:12.998  INFO 91583 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown initiated...
2020-10-24 11:22:13.420  INFO 91583 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown completed.
2020-10-24 11:22:13.428  INFO 91583 --- [           main] ConditionEvaluationReportLoggingListener : 

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2020-10-24 11:22:13.434 ERROR 91583 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [ingredient_categories]

我无法确定这是一个Hibernate问题、一个飞行路线问题还是一个测试问题。

这只是测试“启动”应用程序:

@SpringBootTest
@Testcontainers
class DataApplicationTests {

    @Test
    void contextLoads() {
    }

}

我环顾了一下，可以看到很多人在Spring 2x之前就遇到了一个问题，在flyway生成模式之前验证了表……但这似乎已经“修复”了，默认情况是flyway迁移在之前运行。

我认为问题显示Hibernate的行期望一个表名模式验证：缺少表[ingredient_categories]，所以它似乎没有使用javax.constaint.Table @Table（名称=“成分类别”）注释来运行和构建上下文/豆。

应用程序属性并不太令人兴奋...我正在使用测试容器：

#=========INTEGRATION TESTS========#

## Using TestContainers
spring.datasource.url=jdbc:tc:mysql:8.0.22:///

# Validate Schema
spring.jpa.hibernate.ddl-auto = validate

logging.level.org.flywaydb=DEBUG

Answer 1

来自官方文件

默认情况下，Spring启动使用“Spring物理命名策略”配置物理命名策略。此实现提供与 Hibernate 4 相同的表结构：所有点都替换为下划线，骆驼大小写也替换为下划线。默认情况下，所有表名都以小写形式生成，但如果架构需要该标志，则可以覆盖该标志。

例如，TelephoneNumber实体映射到telephone_number表。

因此< code > ingredient categories 变成了< code > ingredient _ categories 。对于数据库表名，一般约定使用snake-case。您可以在snake case中创建带有名称的表

CREATE TABLE `ingredient_categories`

或者，如果您更喜欢使用Hibernate 5的默认值，请设置以下属性：

spring.jpa.hibernate.naming.physical-strategy=org.hibernate.boot.model.naming.PhysicalNamingStrategyStandardImpl

然后您的表的名称仍然是Ingredient类别，如@Table注释中所示。有关Hibernate 5命名策略配置的详细信息