Most probably such behaviour occurs when you have bidirectional relationship and you’re not synchronizing both sides WHILE having both parent and child persisted (attached to the current session). This is tricky and I’m gonna explain this with the following example. @Entity public class Parent { @Id @GeneratedValue(strategy = IDENTITY) @Column(name = “id”, unique = true, … Read more
You can try below query. Static Imports import static org.springframework.data.mongodb.core.aggregation.Aggregation.*; import static org.springframework.data.mongodb.core.aggregation.ArrayOperators.Filter.filter; import static org.springframework.data.mongodb.core.aggregation.ComparisonOperators.Eq.valueOf; Code Aggregation aggregation = newAggregation( project().and(filter(“parts”) .as(“item”) .by(valueOf( “item.currentState”) .equalToValue( “Estimation Confirmed”))) .as(“parts”); ); List<outputType> results = mongoTemplate.aggregate(aggregation, inputType, outputType)
The easiest way is to use the countQuery attribute of the the @Query annotation to provide a custom query to be used. @Query(value = “SELECT v FROM VisitEntity v LEFT JOIN FETCH v.comments …”, countQuery = “select count(v) from VisitEntity v where …”) List<VisitEntity> getVenueVisits(@Param(“venueId”) long venueId, …);
As @Naros said, the question as it is currently in the title doesn’t really work. It seems we should really look at 4 options and mostly list the pros of each approach, the cons are the absence of the pros of the other: JDBC without Spring Data You get 100% fine-grained control over what is … Read more
new TypeReference<Page<StoryResponse>>() {} The problem with this statement is that Jackson cannot instantiate an abstract type. You should give Jackson the information on how to instantiate Page with a concrete type. But its concrete type, PageImpl, has no default constructor or any @JsonCreators for that matter, so you can not use the following code either: … Read more
Ah, right after I posted this question a section of the spring data docs caught my eye: 73.5 Configure JPA properties In addition all properties in spring.jpa.properties.* are passed through as normal JPA properties (with the prefix stripped) when the local EntityManagerFactory is created. So, to answer my own question: prefix the javax.persistence properties with … Read more
I had a similar use case during testing hibernate event listeners which are only called on commit. The solution was to wrap the code to be persistent into another method annotated with REQUIRES_NEW. (In another class) This way a new transaction is spawned and a flush/commit is issued once the method returns. Keep in mind … Read more
Deprecated answer (Spring Data JPA <=1.6.x): @Modifying annotation to the rescue. You will need to provide your custom SQL behaviour though. public interface UserRepository extends JpaRepository<User, Long> { @Modifying @Query(“delete from User u where u.firstName = ?1”) void deleteUsersByFirstName(String firstName); } Update: In modern versions of Spring Data JPA (>=1.7.x) query derivation for delete, remove … Read more
tl;dr To make it short – there’s no way to unit test Spring Data JPA repositories reasonably for a simple reason: it’s way to cumbersome to mock all the parts of the JPA API we invoke to bootstrap the repositories. Unit tests don’t make too much sense here anyway, as you’re usually not writing any … Read more
public interface StudentDAO extends JpaRepository<StudentEntity, Integer> { public List<StudentEntity> findAllByOrderByIdAsc(); } The code above should work. I’m using something similar: public List<Pilot> findTop10ByOrderByLevelDesc(); It returns 10 rows with the highest level. IMPORTANT: Since I’ve been told that it’s easy to miss the key point of this answer, here’s a little clarification: findAllByOrderByIdAsc(); // don’t miss … Read more