spring-data-jpa
spring-data-jpa copied to clipboard
Simplifies the development of creating a JPA-based data access layer.
**[Jonas Tänzer](https://jira.spring.io/secure/ViewProfile.jspa?name=jtaenzer)** opened **[DATAJPA-1737](https://jira.spring.io/browse/DATAJPA-1737?redirect=false)** and commented Consider the following repository: ```java public interface BookErrorRepository extends Repository { @Query("FROM BookError b WHERE portal = :portal AND date >= :startDate AND date
findAllFetch method causes the following error. however, findAllNotFetch method does not cause errors. because the automatically generated countQuery does not include the fetch keyword. likewise, fetch join paging using @EntityGraph...
I have asked this [question ](https://stackoverflow.com/questions/70610170/hibernate-throws-arrayindexoutofboundsexception-on-some-native-queries) in stack overflow. However, since this really looks like a bug in spring I am also creating this issue: I am using Java 11...
**[Sviataslau Apanasionak](https://jira.spring.io/secure/ViewProfile.jspa?name=slavick)** opened **[DATAJPA-1572](https://jira.spring.io/browse/DATAJPA-1572?redirect=false)** and commented Given following entities: ```java @Entity public class User { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; @ManyToOne(fetch = FetchType.LAZY) @JoinColumn private Room room; }...
**[Praveen](https://jira.spring.io/secure/ViewProfile.jspa?name=JIRAUSER50830)** opened **[DATAJPA-1836](https://jira.spring.io/browse/DATAJPA-1836?redirect=false)** and commented Im using JPA stored procedure query to invoke a oracle 12c stored procedure which has 3 in and 3 out params , out of which...
**[Ihor Herasymenko](https://jira.spring.io/secure/ViewProfile.jspa?name=JIRAUSER50559)** opened **[DATAJPA-1797](https://jira.spring.io/browse/DATAJPA-1797?redirect=false)** and commented Reproducible with the latest Spring Data (Neumann-SR4) and Spring Framework 5.2.9. Not reproducible with the latest Spring Data (Neumann-SR4) and Spring Framework 5.2.5. Looks...
Using tuples makes spring data responsible for selecting the right thing and doesn't work for collection valued attributes at all. See #2078, #1623
**[Jens Schauder](https://jira.spring.io/secure/ViewProfile.jspa?name=schauder)** opened **[DATAJPA-1551](https://jira.spring.io/browse/DATAJPA-1551?redirect=false)** and commented There are various issues that try to make some kind of customisation possible for queries. Most of these are somewhat ad hoc in that...