如何编写具有多个连接的 Spring 数据 JPA 规范?
How to write a Spring Data JPA Specification with multiple joins?
我正在处理的项目是使用支持实体过滤的 JHipster 生成的,它在后台使用 Spring Data JPA 规范。
模型如下(JDL):
entity Student {
name String
}
entity Course {
name String
}
entity Enrollment {
}
entity Attendance {
date LocalDate
}
relationship OneToMany {
Student to Enrollment(student required),
Course to Enrollment(course required),
Enrollment to Attendance(enrollment required)
}
filter all
service all with serviceClass
JHipster 生成用于通过 enrollmentId
过滤 Attendance
的样板,但我想扩展它以能够通过 studentId
和 courseId
过滤。
那么,我如何实现一个规范来执行如下查询:
SELECT
attendance.date, student.name as student, course.name as course
FROM attendance
JOIN enrollment
ON enrollment.id = attendance.enrollment_id
JOIN student
ON student.id = enrollment.student_id
AND studend.id = 1
JOIN course
ON course.id = enrollment.course_id
AND course.id = 2;
听从 @GaëlMarziou 的建议,我实现了创建 Specification<Attendance>
的简单方法,用于与 Student
和 Course
连接。
我将字段、getter 和 setter 添加到 AttendanceCriteria
class,并重新编译以更新 JPA 元模型:
private LongFilter studentId;
private LongFilter courseId;
public LongFilter getStudentId() {
return studentId;
}
public void setStudentId(LongFilter studentId) {
this.studentId = studentId;
}
public LongFilter getCourseId() {
return courseId;
}
public void setCourseId(LongFilter courseId) {
this.courseId = courseId;
}
这是来自 AttencanceQueryService
class 的更新片段:
private Specification<Attendance> createSpecification(AttendanceCriteria criteria) {
Specification<Attendance> specification = Specification.where(null);
if (criteria != null) {
if (criteria.getId() != null) {
specification = specification.and(buildSpecification(criteria.getId(), Attendance_.id));
}
if (criteria.getDate() != null) {
specification = specification.and(buildRangeSpecification(criteria.getDate(), Attendance_.date));
}
if (criteria.getEnrollmentId() != null) {
specification = specification.and(buildReferringEntitySpecification(criteria.getEnrollmentId(), Attendance_.enrollment, Enrollment_.id));
}
if (criteria.getStudentId() != null) {
specification = specification.and(buildJoinSpecification(criteria.getStudentId(), Attendance_.enrollment, Enrollment_.student, Student_.id));
}
if (criteria.getCourseId() != null) {
specification = specification.and(buildJoinSpecification(criteria.getCourseId(), Attendance_.enrollment, Enrollment_.course, Course_.id));
}
}
return specification;
}
private <REFERENCE, JOIN, FILTER extends Comparable<? super FILTER>> Specification<Attendance> buildJoinSpecification(RangeFilter<FILTER> filter, SingularAttribute<? super Attendance, REFERENCE> reference, SingularAttribute<REFERENCE, JOIN> joinField, SingularAttribute<JOIN, FILTER> valueField) {
Specification<Attendance> result = Specification.where((Specification) null);
if (filter.getEquals() != null) {
result = this.equalsSpecification(reference, joinField, valueField, filter.getEquals());
}
if (filter.getIn() != null) {
result = this.valueIn((SingularAttribute) reference, joinField, valueField, filter.getIn());
}
return result;
}
private <REFERENCE, JOIN, FILTER> Specification<Attendance> equalsSpecification(SingularAttribute<? super Attendance, REFERENCE> reference, SingularAttribute<REFERENCE, JOIN> joinField, SingularAttribute<JOIN, FILTER> idField, FILTER value) {
return (root, query, builder) ->
builder.equal(root.join(reference).join(joinField).get(idField), value);
}
private <REFERENCE, JOIN, FILTER> Specification<Attendance> valueIn(SingularAttribute<? super Attendance, REFERENCE> reference, SingularAttribute<REFERENCE, JOIN> joinField, SingularAttribute<JOIN, FILTER> valueField, Collection<FILTER> values) {
return (root, query, builder) -> {
CriteriaBuilder.In<FILTER> in = builder.in(root.join(reference).join(joinField).get(valueField));
for (FILTER value : values) {
in = in.value(value);
}
return in;
};
}
我希望这对某人有所帮助,感谢 @GaëlMarziou 和 Blackdread/Yoann Caplain.
我正在处理的项目是使用支持实体过滤的 JHipster 生成的,它在后台使用 Spring Data JPA 规范。
模型如下(JDL):
entity Student {
name String
}
entity Course {
name String
}
entity Enrollment {
}
entity Attendance {
date LocalDate
}
relationship OneToMany {
Student to Enrollment(student required),
Course to Enrollment(course required),
Enrollment to Attendance(enrollment required)
}
filter all
service all with serviceClass
JHipster 生成用于通过 enrollmentId
过滤 Attendance
的样板,但我想扩展它以能够通过 studentId
和 courseId
过滤。
那么,我如何实现一个规范来执行如下查询:
SELECT
attendance.date, student.name as student, course.name as course
FROM attendance
JOIN enrollment
ON enrollment.id = attendance.enrollment_id
JOIN student
ON student.id = enrollment.student_id
AND studend.id = 1
JOIN course
ON course.id = enrollment.course_id
AND course.id = 2;
听从 @GaëlMarziou 的建议,我实现了创建 Specification<Attendance>
的简单方法,用于与 Student
和 Course
连接。
我将字段、getter 和 setter 添加到 AttendanceCriteria
class,并重新编译以更新 JPA 元模型:
private LongFilter studentId;
private LongFilter courseId;
public LongFilter getStudentId() {
return studentId;
}
public void setStudentId(LongFilter studentId) {
this.studentId = studentId;
}
public LongFilter getCourseId() {
return courseId;
}
public void setCourseId(LongFilter courseId) {
this.courseId = courseId;
}
这是来自 AttencanceQueryService
class 的更新片段:
private Specification<Attendance> createSpecification(AttendanceCriteria criteria) {
Specification<Attendance> specification = Specification.where(null);
if (criteria != null) {
if (criteria.getId() != null) {
specification = specification.and(buildSpecification(criteria.getId(), Attendance_.id));
}
if (criteria.getDate() != null) {
specification = specification.and(buildRangeSpecification(criteria.getDate(), Attendance_.date));
}
if (criteria.getEnrollmentId() != null) {
specification = specification.and(buildReferringEntitySpecification(criteria.getEnrollmentId(), Attendance_.enrollment, Enrollment_.id));
}
if (criteria.getStudentId() != null) {
specification = specification.and(buildJoinSpecification(criteria.getStudentId(), Attendance_.enrollment, Enrollment_.student, Student_.id));
}
if (criteria.getCourseId() != null) {
specification = specification.and(buildJoinSpecification(criteria.getCourseId(), Attendance_.enrollment, Enrollment_.course, Course_.id));
}
}
return specification;
}
private <REFERENCE, JOIN, FILTER extends Comparable<? super FILTER>> Specification<Attendance> buildJoinSpecification(RangeFilter<FILTER> filter, SingularAttribute<? super Attendance, REFERENCE> reference, SingularAttribute<REFERENCE, JOIN> joinField, SingularAttribute<JOIN, FILTER> valueField) {
Specification<Attendance> result = Specification.where((Specification) null);
if (filter.getEquals() != null) {
result = this.equalsSpecification(reference, joinField, valueField, filter.getEquals());
}
if (filter.getIn() != null) {
result = this.valueIn((SingularAttribute) reference, joinField, valueField, filter.getIn());
}
return result;
}
private <REFERENCE, JOIN, FILTER> Specification<Attendance> equalsSpecification(SingularAttribute<? super Attendance, REFERENCE> reference, SingularAttribute<REFERENCE, JOIN> joinField, SingularAttribute<JOIN, FILTER> idField, FILTER value) {
return (root, query, builder) ->
builder.equal(root.join(reference).join(joinField).get(idField), value);
}
private <REFERENCE, JOIN, FILTER> Specification<Attendance> valueIn(SingularAttribute<? super Attendance, REFERENCE> reference, SingularAttribute<REFERENCE, JOIN> joinField, SingularAttribute<JOIN, FILTER> valueField, Collection<FILTER> values) {
return (root, query, builder) -> {
CriteriaBuilder.In<FILTER> in = builder.in(root.join(reference).join(joinField).get(valueField));
for (FILTER value : values) {
in = in.value(value);
}
return in;
};
}
我希望这对某人有所帮助,感谢 @GaëlMarziou 和 Blackdread/Yoann Caplain.