Is it possible to use Hibernate and Mysql with ReactiveCrudRepository instead of CrudRepository? TL;DR: Not with Hibernate and MySQL, but with R2DBC and Postgres, Microsoft SQL Server or H2. Take a look at Spring Data R2DBC. Long Version Why not JPA? With Hibernate/JPA included this won’t happen in the foreseeable future. JPA is based on … Read more
I had the same issue. I wanted my schema to be created by hibernate because of it’s database independence. I already went through the trouble of figuring out a nice schema for my application in my jpa classes, I don’t like repeating myself. But I want some data initialization to be done in a versioned … Read more
You should use TransactionTemplate object to manage transaction imperatively: transactionTemplate.execute( status -> em.createNativeQuery(“TRUNCATE TABLE MyTable”).executeUpdate()); To create TransactionTemplate just use injected PlatformTransactionManager: transactionTemplate = new TransactionTemplate(platformTransactionManager); And if you want to use new transaction just invoke transactionTemplate.setPropagationBehavior( TransactionDefinition.PROPAGATION_REQUIRES_NEW);
Just add the following to your user repository interface void deleteByIdIn(List<Integer> ids); Spring will automatically generate the appropriate query via method name derivation. https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.query-methods EDIT: A litte more detail on this Using Springs Repository interfaces like CrudRepository, JpaRespository brings the basic set of database operations, like create, read, update, delete, paging, sorting and so on. … Read more
You’re using a recent version of Hikari CP and the connection leak resolves by itself (as visible in your logs). As noted by @M. Deinum the issue can be caused in a low value of hikari.leakDetectionThreshold property (your “in” query can take much more than 2 seconds). Try to increase it to 60000, then do … Read more
Is the delete not working or not working as how you’d expect? Typically an entity has to be managed before it can be deleted, so a JPA provider (hibernate in your case) will load (the query you see) the entity first, then issue the delete. If you’re only seeing the query, but no corresponding delete, … Read more
Spring added this future as well. Just make oneIndexed parameter equals to true in your configuration file and pagination will start from page 1.By default its false and pagination starts from 0. spring.data.web.pageable.one-indexed-parameters=true
The only part of it you can parameterise are values used in WHERE clause. Consider this sample from official doc: public interface UserRepository extends JpaRepository<User, Long> { @Query(value = “SELECT * FROM USERS WHERE EMAIL_ADDRESS = ?1”, nativeQuery = true) User findByEmailAddress(String emailAddress); }
I believe this post answers your question: Why to use returned instance after save() on Spring Data JPA Repository? The repository.save() method actually returns a new object like JPA entityManager.merge() and the returned object is the one that will have the ID set.
Try this parameter description: List<ShopOrder> getShopOrder(@Param(“id”) long id);