<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spring JPA on Adrien CAUBEL</title><link>https://blog.adriencaubel.fr/series/spring-jpa/</link><description>Recent content in Spring JPA on Adrien CAUBEL</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 08 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.adriencaubel.fr/series/spring-jpa/index.xml" rel="self" type="application/rss+xml"/><item><title>Spring Data JPA: Combine Projection and Specification</title><link>https://blog.adriencaubel.fr/posts/spring/spring_jpa_combime_projection_and_specification/</link><pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate><guid>https://blog.adriencaubel.fr/posts/spring/spring_jpa_combime_projection_and_specification/</guid><description>Tip GitHub project : https://github.com/Adrien-Courses/Spring-jpa-specification-projection For a long time, combining a Specification (dynamic filtering) with a Projection (selecting only the columns you need) was considered impossible in Spring Data JPA. The usual answer on StackOverflow was:
Starting from Spring Data 3.0, mixing projections and specifications is supported. [&amp;hellip; BUT &amp;hellip;] the generated SQL still queries all the columns
This is no longer true. In this article we review projections, specifications, and how to combine them while keeping a narrow SQL query.</description></item></channel></rss>