SpringDataJpa写原生sql遇到的问题及解决

SpringDataJpa写原生sql遇到的问题及解决

目录SpringDataJpa写原生sql遇到的问题Spring data jpa 自定义SQL语句遇到错误Not supported for DML operations

SpringDataJpa写原生sql遇到的问题

@Repository

public interface EduCourseDao extends JpaRepository, JpaSpecificationExecutor {

//根据课程id查询课程的确认信息

@Query(value = "SELECT ec.id,ec.title,ec.price,ec.lesson_num, " +

"ecd.description, " +

"es1.title AS oneSubject, " +

"es2.title AS twoSubject " +

"FROM edu_course ec LEFT JOIN edu_course_description ecd ON ec.id=ecd.id " +

"LEFT JOIN edu_teacher et ON ec.teacher_id=et.id " +

"LEFT JOIN edu_subject es1 ON ec.subject_parent_id=es1.id " +

"LEFT JOIN edu_subject es2 ON ec.subject_id=es2.id " +

"WHERE ec.id=?1 ",nativeQuery = true)

List< Map> findPublishInfoById(String id);

}

因为涉及到其他表，所以返回类型使用List< Map> ，而不是用原先定义的vo类

每行最后的，与 " 之间要有一个空格，不然报错。

Spring data jpa 自定义SQL语句遇到错误

Not supported for DML operations

今天在自定义一个Update语句时运行遇到一个错误，显示Not supported for DML operations 也就是说不支持DML操作。

我的UserRepository是继承的PagingAndSortingRepository接口，在看了JPA的文档之后，发现此接口不支持update事务，所以需要在注解上添加@Modifying。

3.3.7. Modifying queries

All the sections above describe how to declare queries to access a given entity or collection of entities.Of course you can add custom modifying behaviour by using facilities described in Customimplementations for Spring Data repositories. As this approach is feasible for comprehensive customfunctionality, you can achieve the execution of modifying queries that actually only need parameterbinding by annotating the query method with @Modifying:

Example 45. Declaring manipulating queries

@Modifying

@Query("update User u set u.firstname = ?1 where u.lastname = ?2")

int setFixedFirstnameFor(String firstname, String lastname);

This will trigger the query annotated to the method as updating query instead of a selecting one. As theEntityManager might contain outdated entities after the execution of the modifying query, we do notautomatically clear it (see javaDoc of EntityManager.clear() for details) since this will effectively dropall non-flushed changes still pending in the EntityManager. If you wish the EntityManager to be clearedautomatically you can set @Modifying annotation's clearAutomatically attribute to true.

以下是我的源码：

@Modifying

@Query("update User u set u.u_name=?2,u.u_sex=?3,u.u_date = ?4,u.u_minzu = ?5,u.u_area=?6,u.u_country=?7 where u.u_id =?1")

public void updateUserById(String u_id,String u_name,String u_sex,

String u_date, String u_minzu,String u_area,

String u_country);

版权声明：本文内容由网络用户投稿，版权归原作者所有，本站不拥有其著作权，亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容，请联系我们jiasou666@gmail.com 处理，核实后本网站将在24小时内删除侵权内容。