Hibernate中嵌入式类的@NotNull注解不生效问题排查
问题描述
我定义了以下两个JPA实体类和嵌入式类:
Address 嵌入式类
import javax.persistence.Embeddable; import javax.validation.constraints.NotNull; import javax.validation.constraints.Size; @Embeddable public class Address { @NotNull @Size(max = 50) private String street; }
User 实体类
import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.Table; import javax.validation.Valid; import javax.validation.constraints.NotNull; @Entity @Table(name = "USERS") public class User { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; @NotNull private String username; @Valid private Address homeAddress; }
生成的MySQL表结构如下:
CREATE TABLE `USERS` ( `id` bigint NOT NULL AUTO_INCREMENT, `street` varchar(50) DEFAULT NULL, `username` varchar(255) NOT NULL, PRIMARY KEY (`id`) )
可以看到username字段的@NotNull约束生效(生成了NOT NULL),嵌入式类的@Size(max = 50)也生效(varchar(50)),但嵌入式类中street字段的@NotNull却没有生成对应的NOT NULL约束,请问我遗漏了什么?
相关的pom.xml配置:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.manning.javapersistence</groupId> <artifactId>mapping-value-types</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>mapping-value-types</name> <url>http://maven.apache.org</url> <build> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>3.10.1</version> <configuration> <source>17</source> <target>17</target> </configuration> </plugin> <plugin> <artifactId>maven-surefire-plugin</artifactId> <version>2.22.2</version> <configuration> <includes> <include>**/*.java</include> </includes> </configuration> </plugin> </plugins> </build> <dependencies> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> <version>5.6.9.Final</version> </dependency> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-engine</artifactId> <version>5.8.2</version> <scope>test</scope> </dependency> <dependency> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> <version>8.0.29</version> </dependency> <dependency> <groupId>org.springframework.data</groupId> <artifactId>spring-data-jpa</artifactId> <version>2.7.0</version> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-test</artifactId> <version>5.3.20</version> </dependency> <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.el</artifactId> <version>3.0.0</version> </dependency> <dependency> <groupId>javax.validation</groupId> <artifactId>validation-api</artifactId> <version>2.0.1.Final</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator</artifactId> <version>6.2.3.Final</version> </dependency> </dependencies> </project>
解决方案
问题出在Bean Validation约束与JPA DDL生成的映射规则差异上:
@NotNull的双重作用差异:
- 对于实体类的直接属性(比如
User.username),Hibernate默认会将Bean Validation的@NotNull转换为数据库列的NOT NULL约束。 - 但对于嵌入式类(
@Embeddable)的属性(比如Address.street),Hibernate默认不会自动将@NotNull映射为数据库的NOT NULL约束——因为嵌入式对象本身允许为null(比如User.homeAddress可以是null,此时对应的street列自然会是null)。
- 对于实体类的直接属性(比如
两种可行解决方式:
- 方式一:显式添加JPA的
@Column(nullable = false):
直接在Address.street字段上添加该注解,强制生成数据库的非空约束:@Embeddable public class Address { @NotNull @Size(max = 50) @Column(nullable = false) // 新增该注解 private String street; } - 方式二:确保嵌入式对象本身不可为空:
如果业务要求homeAddress永远不能为null,可以在User.homeAddress上添加@NotNull,同时保留Address.street的@NotNull。不过这种方式仅能保证运行时Bean Validation生效,若要生成DDL约束,仍需配合@Column(nullable = false):public class User { // ...其他属性 @Valid @NotNull // 新增该注解,确保homeAddress不为null private Address homeAddress; }
- 方式一:显式添加JPA的
关于
@Valid的作用说明:
你添加的@Valid仅用于触发运行时的级联Bean Validation——当保存User时,如果homeAddress不为null,会校验street的@NotNull约束,但这和数据库DDL约束的生成无关。
内容的提问来源于stack exchange,提问作者Matías Santurio
相关产品推荐
相关产品推荐

