Skip To Main Content
return query.getResult List on Muck Rack

return query.getResult List

As seen in: InfoQ
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with return query.getResult

Contact return query.getResult, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

Spring Data JPA Custom Repository

|
By return query.getResult List, string memberName, Long teamId
| velog.io
Custom Repository란 무엇인가 Spring Data JPA는 인터페이스만 정의하면 기본적인 CRUD 메서드와 쿼리 메서드를 자동으로 제공합니다. 하지만 실무에서는 Spring Data JPA의 기본 기능만으로 해결하기 어려운 복잡한 요구사항이 발생합니다. 동적 쿼리, 복잡한 통계 쿼리, 특정 데이터베이스에 최적화된 쿼리 등이 그 예입니다. 이런 경우 Custom Repository(사용자 정의 리포지토리)를 구현하여 해결할 수 있습니다. Custom Repository는 Spring Data JPA의 자동 구현 기능을 유지하면서, 직접 구현한 메서드를 추가할 수 있게 해줍니다. JpaRepository의 편리함과 직접 구현의 유연함을 모두 활용할 수 있습니다.
Open in Who Shared Issue with article?

Architecting with Java Persistence: Patterns and Strategies

|
By List address, List findAll, Otavio Santana, return query.getResult List
| InfoQ Verified
Java persistence patterns like Driver, Mapper, DAO, Active Record, and Repository are crucial for robust database interaction and application architecture, with each offering distinct data management approaches. Balancing layers is essential for managing complexity and optimizing data flow, with each pattern having its own set of advantages and disadvantages to consider for informed architectural decisions.
Open in Who Shared Issue with article?
See all 2 articles