Fix handling of null predicate in Specification.not().

When toPredicate() returns null, Specification.not() now returns
builder.disjunction() instead of builder.not(null). This change
ensures proper handling of null predicates in negated specifications.

Closes #3849
Original pull request: #3856

Signed-off-by: SWQXDBA <[email protected]>

Author: SWQXDBA

spring-data-jpa/src/main/java/org/springframework/data/jpa/domain/Specification.java

@@ -156,7 +156,7 @@ static <T> Specification<T> not(Specification<T> spec) {
 		return (root, query, builder) -> {
 
 			Predicate predicate = spec.toPredicate(root, query, builder);
-			return predicate != null ? builder.not(predicate) : null;
+			return predicate != null ? builder.not(predicate) : builder.disjunction();
 		};
 	}
 

spring-data-jpa/src/test/java/org/springframework/data/jpa/domain/SpecificationUnitTests.java

@@ -139,6 +139,17 @@ void orCombinesSpecificationsInOrder() {
 		verify(builder).or(firstPredicate, secondPredicate);
 	}
 
+	@Test // #3849
+	void notWithNullPredicate() {
+		Specification<Object> spec = (r, q, cb) -> null;
+
+		Specification<Object> notSpec = Specification.not(spec);
+
+		notSpec.toPredicate(root, query, builder);
+		
+		verify(builder).disjunction();
+	}
+
 	static class SerializableSpecification implements Serializable, Specification<Object> {
 
 		@Override