PricingLoginStart free
Spring Boot 4 Complete Guide · Aula

JPQL e consultas nativas com @Query

Escreva consultas JPQL e SQL nativo explícitas, associe parâmetros nomeados e posicionais e mapeie projeções.

Aula 2 de 413 etapas

JPQL e consultas nativas com @Query é uma aula grátis de Spring Boot 4 Complete Guide no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Spring Boot 4 Complete Guide, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Spring Boot 4 Complete Guide inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Why @Query Exists

Spring Data JPA can derive queries from method names like findByLastName, but derived queries break down for anything non-trivial: joins across entities, aggregations, custom projections, or fine-tuned SQL.

The @Query annotation lets you attach an explicit query to a repository method. You write the query once, declaratively, and Spring binds the method's parameters and maps the result.

  • JPQL — object-oriented query language that works against entities and fields.
  • Native SQL — raw database SQL when you need vendor features or hand-tuned queries.

A Basic JPQL @Query

JPQL looks like SQL but operates on entity names and Java field names, not table and column names. Here User is the entity class and email is a Java field.

Notice the placeholder ?1 — this is a positional parameter bound to the first method argument.

public interface UserRepository extends JpaRepository<User, Long> {

    @Query("SELECT u FROM User u WHERE u.email = ?1")
    Optional<User> findByEmailAddress(String email);
}

Named Parameters with @Param

Positional parameters (?1, ?2) work, but they break when you reorder arguments. Named parameters are clearer and safer: write :name in the query and bind it with @Param("name").

  • The string in @Param must match the :placeholder exactly.
  • Order of method arguments no longer matters.
public interface UserRepository extends JpaRepository<User, Long> {

    @Query("SELECT u FROM User u WHERE u.status = :status AND u.age >= :minAge")
    List<User> findActiveAdults(@Param("status") String status,
                               @Param("minAge") int minAge);
}

Named vs Positional — Which to Use

Both styles bind method arguments into the query, but they differ in maintainability.

  • Positional (?1) — concise for one or two params; fragile when you add or reorder arguments.
  • Named (:status) — self-documenting and resilient to refactoring; preferred for queries with multiple parameters.

The team standard in Spring Boot 4 projects is to favor named parameters for readability. Reserve positional parameters for very short queries.

Native SQL Queries

When you need database-specific SQL — window functions, vendor extensions, or a hand-optimized statement — set nativeQuery = true. Now the query runs as raw SQL against table and column names, not entity fields.

The result is still mapped back to the User entity because the selected columns match the entity's table.

public interface UserRepository extends JpaRepository<User, Long> {

    @Query(value = "SELECT * FROM users WHERE email = :email",
           nativeQuery = true)
    Optional<User> findByEmailNative(@Param("email") String email);
}

JPQL vs Native — Picking the Right Tool

Default to JPQL; reach for native SQL only when JPQL can't express what you need.

  • JPQL — portable across databases, refactor-safe (uses Java field names), integrates with the persistence context.
  • Native — full SQL power and vendor features, but ties you to one database dialect and bypasses some JPA conveniences.

A common pitfall: in native queries LIKE wildcards and pagination must follow your database's SQL, not JPQL rules.

Interface-Based Projections

Often you don't need the whole entity — just a few columns. A projection returns a lightweight view instead of a full User.

Define an interface with getters; Spring matches each getter to a selected alias. This loads only the columns you ask for.

public interface UserSummary {
    String getName();
    String getEmail();
}

public interface UserRepository extends JpaRepository<User, Long> {

    @Query("SELECT u.name AS name, u.email AS email FROM User u WHERE u.active = true")
    List<UserSummary> findActiveSummaries();
}

Aliases Matter for Projections

For an interface projection to bind, each selected expression must be aliased to match the getter name. The getter getEmail() maps to alias email.

  • SELECT u.email AS email binds to getEmail().
  • Omitting the alias on a computed column leaves the getter unmapped and returns null.

This holds for both JPQL and native projection queries.

DTO Projections with Constructor Expressions

JPQL also supports constructor expressions: build a DTO directly in the query with the NEW keyword. You must use the fully-qualified class name and match a constructor's parameter order.

This gives you an immutable, typed result object instead of an interface proxy.

public record UserDto(String name, String email) {}

public interface UserRepository extends JpaRepository<User, Long> {

    @Query("SELECT new com.example.app.UserDto(u.name, u.email) FROM User u WHERE u.active = true")
    List<UserDto> findActiveDtos();
}

Modifying Queries

@Query can also run UPDATE and DELETE statements. These require @Modifying so Spring executes them as updates rather than selects, and they typically run inside a @Transactional method.

The return value is the count of affected rows.

public interface UserRepository extends JpaRepository<User, Long> {

    @Modifying
    @Transactional
    @Query("UPDATE User u SET u.status = :status WHERE u.lastLogin < :cutoff")
    int deactivateStale(@Param("status") String status,
                        @Param("cutoff") LocalDate cutoff);
}

A Standalone JPQL Mental Model

JPQL parameter binding mirrors how you'd substitute values yourself. The snippet below is plain Java that demonstrates the named-parameter substitution idea behind :status and :minAge — no database required.

In real code Spring does this binding safely via prepared statements; this just illustrates the concept.

import java.util.Map;

public class ParamBindingDemo {
    static String bind(String query, Map<String, String> params) {
        for (Map.Entry<String, String> e : params.entrySet()) {
            query = query.replace(":" + e.getKey(), e.getValue());
        }
        return query;
    }

    public static void main(String[] args) {
        String jpql = "SELECT u FROM User u WHERE u.status = :status AND u.age >= :minAge";
        Map<String, String> params = Map.of("status", "'ACTIVE'", "minAge", "18");
        System.out.println(bind(jpql, params));
    }
}

Quick Check

Test your understanding of @Query parameter binding and projections.

Responda na aula interativa

Recap

You now know how to write explicit queries with @Query:

  • JPQL works on entity and field names; native SQL (nativeQuery = true) works on tables and columns.
  • Bind values with positional (?1) or, preferably, named (:name + @Param) parameters.
  • Interface projections need aliases matching getter names; constructor expressions (SELECT new ...) build typed DTOs.
  • Use @Modifying (with @Transactional) for UPDATE/DELETE queries.

Default to JPQL for portability; drop to native SQL only when you truly need database-specific power.

Grátis para começar

Aprenda Java com um tutor de IA — grátis

Escreva e execute código real no seu navegador, obtenha ajuda instantânea de um tutor de IA 24/7 e continue de onde parou na web ou no app.

Cursos
21
Aulas
84
Começar a aprender grátisVer o curso completo

Perguntas Frequentes

A aula “JPQL e consultas nativas com @Query” é grátis?

Sim — o texto completo de “JPQL e consultas nativas com @Query” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Spring Boot 4 Complete Guide, atualize para CoddyKit PRO. O curso de Spring Boot 4 Complete Guide inclui 4 aulas no total.

O que vou aprender em “JPQL e consultas nativas com @Query”?

Escreva consultas JPQL e SQL nativo explícitas, associe parâmetros nomeados e posicionais e mapeie projeções. Você pratica Spring Boot 4 Complete Guide com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Spring Boot 4 Complete Guide?

Nenhuma experiência prévia é necessária. Spring Boot 4 Complete Guide no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “JPQL e consultas nativas com @Query”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Spring Boot 4 Complete Guide?

Sim. Cada aula de Spring Boot 4 Complete Guide inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Métodos de consulta derivados e resolução de palavras-chave
  2. JPQL e consultas nativas com @Query
  3. Especificações e filtragem dinâmica baseada em critérios
  4. Paginação, ordenação e transmissão de fatias
← Voltar para Spring Boot 4 Complete Guide