使用CriteriaBuilder编写Spring Data JPA规范并处理一对多关系

16

我有一个User实体,一个UserToApplication实体和一个Application实体。

一个User可以访问多个Application,一个Application也可以被多个User使用。

这是User实体。

@Entity
@Table(name = "USER", schema = "UDB")
public class User {
    private Long userId;
    private Collection<Application> applications;
    private String firstNm;
    private String lastNm;
    private String email;

    @SequenceGenerator(name = "generator", sequenceName = "UDB.USER_SEQ", initialValue = 1, allocationSize = 1)
    @Id
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "generator")
    @Column(name = "USER_ID", unique = true, nullable = false)
    public Long getUserId() {
        return userId;
    }

    public void setUserId(Long userId) {
        this.userId = userId;
    }

    @OneToMany(mappedBy = "user", fetch = FetchType.LAZY)
    public Collection<Application> getApplications() {
        return applications;
    }

    public void setApplications(Collection<Application> applications) {
        this.applications = applications;
    }

    /* Other getters and setters omitted for brevity */
}

这里是UserToApplication实体。

@Entity
@Table(name = "USER_TO_APPLICATION", schema = "UDB")
public class Application {
    private Long userToApplicationId;
    private User user;
    private Application application;

    @SequenceGenerator(name = "generator", sequenceName = "UDB.USER_TO_APP_SEQ", initialValue = 0, allocationSize = 1)
    @Id
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "generator")
    @Column(name = "USER_TO_APPLICATION_ID", unique = true, nullable = false)
    public Long getUserToApplicationId() {
        return userToApplicationId;
    }

    public void setUserToApplicationId(Long userToApplicationId) {
        this.userToApplicationId = userToApplicationId;
    }

    @ManyToOne
    @JoinColumn(name = "USER_ID", referencedColumnName = "USER_ID", nullable = false)
    public User getUser() {
        return user;
    }

    public void setUser(User user) {
        this.user = user;
    }

    @ManyToOne
    @JoinColumn(name = "APPLICATION_ID", nullable = false)
    public Application getApplication() {
        return application;
    }
}

这里是Application实体。

@Entity
@Table(name = "APPLICATION", schema = "UDB")
public class Application {
    private Long applicationId;
    private String name;
    private String code;

    /* Getters and setters omitted for brevity */
}

我有以下的规格说明 (Specification),用于通过电子邮件搜索用户(User)

public class UserSpecification {

    public static Specification<User> findByFirstNmLastNmEmail(String firstNm, String lastNm, String email) {
        return new Specification<User>() {
            @Override
            public Predicate toPredicate(Root<User> root, CriteriaQuery<?> query, CriteriaBuilder cb) {
                final Predicate firstNmPredicate = null;
                final Predicate lastNmPredicate = null;
                final Predicate emailPredicate = null;

                if (!StringUtils.isEmpty(firstNm)) {
                    firstNmPredicate = cb.like(cb.lower(root.get(User_.firstNm), firstNm));
                }
                if (!StringUtils.isEmpty(lastNm)) {
                    lastNmPredicate = cb.like(cb.lower(root.get(User_.lastNm), lastNm));
                }
                if (!StringUtils.isEmpty(email)) {
                    emailPredicate = cb.like(cb.lower(root.get(User_.email), email));
                }
                return cb.and(firstNmPredicate, lastNmPredicate, emailPredicate);
            }
        };
    }

}

这是我目前拥有的User_元模型。

@StaticMetamodel(User.class)
public class User_ {
    public static volatile SingularAttribute<User, String> firstNm;
    public static volatile SingularAttribute<User, String> lastNm;
    public static volatile SingularAttribute<User, String> email;
}

现在,我还想将应用程序ID列表传递给 Specification ,使得其方法签名为:

public static Specification<User> findByFirstNmLastNmEmailApp(String firstNm, String lastNm, String email, Collection<Long> appIds)

所以,我的问题是,如果我将@OneToMany映射添加到User_元模型中的Collection<Application> applications字段上,那么我该如何在Specification中引用它?

我的当前Specification类似于以下SQL查询:

select * from user u
where lower(first_nm) like '%firstNm%'
and lower(last_nm) like '%lastNm%'
and lower(email) like '%email%';

而我想在新的 规范 中实现的目标是这样的:

select * from user u
join user_to_application uta on uta.user_id = u.user_id
where lower(u.first_nm) like '%firstNm%'
and lower(u.last_nm) like '%lastNm%'
and lower(u.email) like '%email%'
and uta.application_id in (appIds);

这种映射是否可以在元模型中完成,我该如何在我的Specification中实现这个结果?

1个回答

25

我找到了一个解决方案。为了映射一个一对多的属性,在元模型中我添加了以下内容:

public static volatile CollectionAttribute<User, Application> applications;

我还需要为Application实体添加一个元模型。

@StaticMetamodel(Application.class)
public class Application_ {
    public static volatile SingularAttribute<Application, Long> applicationId;
}

那么在我的规范中,我可以使用Root<User>实例上的.join()方法,访问用户的应用程序。以下是我创建的Predicate

final Predicate appPredicate = root.join(User_.applications).get(Application_.applicationId).in(appIds);

值得注意的是,根据我在问题中编写的Specification,如果任何输入值为空,则不会起作用。将空的Predicate传递给CriteriaBuilder.and()方法将导致NullPointerException 。因此,我创建了一个 Predicate 类型的 ArrayList,然后如果相应的参数非空,就将每个Predicate 添加到列表中。最后,我将 ArrayList 转换为数组,以便将其传递给 CriteriaBuilder.and()函数。这是最终的 Specification

public class UserSpecification {

    public static Specification<User> findByFirstNmLastNmEmailApp(String firstNm, String lastNm, String email, Collection<Long> appIds) {
        return new Specification<User>() {
            @Override
            public Predicate toPredicate(Root<User> root, CriteriaQuery<?> query, CriteriaBuilder cb) {
                final Collection<Predicate> predicates = new ArrayList<>();
                if (!StringUtils.isEmpty(firstNm)) {
                    final Predicate firstNmPredicate = cb.like(cb.lower(root.get(User_.firstNm), firstNm));
                    predicates.add(firstNmPredicate);
                }
                if (!StringUtils.isEmpty(lastNm)) {
                    final Predicate lastNmPredicate = cb.like(cb.lower(root.get(User_.lastNm), lastNm));
                    predicates.add(lastNmPredicate);
                }
                if (!StringUtils.isEmpty(email)) {
                    final Predicate emailPredicate = cb.like(cb.lower(root.get(User_.email), email));
                    predicates.add(emailPredicate);
                }
                if (!appIds.isEmpty()) {
                    final Predicate appPredicate = root.join(User_.applications).get(Application_.applicationId).in(appIds);
                    predicates.add(appPredicate);
                }

                return cb.and(predicates.toArray(new Predicate[predicates.size()]));
            }
        };
    }

}

Application_类中的变量声明应该如下所示:public static volatile SingularAttribute<Application,Long> applicationId; 而不是 public static volatile SingularAttribute<User,Long> applicationId; 尽管整体答案是完美的。 - Avi
@Avi谢谢你指出这一点!我已经在我的答案中进行了更正。 - Andrew Mairose
你可能会惊讶地听到,使用大小为零的数组调用Array函数更快。我也很惊讶。https://dev59.com/j3VC5IYBdhLWcg3w0EsD#29444594 - findusl

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接