PricingLoginStart free
Spring Boot 4 Complete Guide · Pelajaran

Kueri JPQL dan Native dengan @Query

Tulis kueri JPQL dan SQL native secara eksplisit, ikat parameter bernama dan posisi, lalu petakan proyeksi.

Pelajaran 2 dari 413 langkah

Kueri JPQL dan Native dengan @Query adalah pelajaran Spring Boot 4 Complete Guide gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Spring Boot 4 Complete Guide, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Spring Boot 4 Complete Guide mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

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.

Jawab di pelajaran interaktif

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.

Gratis untuk memulai

Belajar Java dengan tutor AI — gratis

Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.

Kursus
21
Pelajaran
84
Mulai belajar gratisLihat kursus lengkapnya

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Kueri JPQL dan Native dengan @Query” gratis?

Ya — teks lengkap “Kueri JPQL dan Native dengan @Query” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Spring Boot 4 Complete Guide, upgrade ke CoddyKit PRO. Kursus Spring Boot 4 Complete Guide mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Kueri JPQL dan Native dengan @Query”?

Tulis kueri JPQL dan SQL native secara eksplisit, ikat parameter bernama dan posisi, lalu petakan proyeksi. Kamu berlatih Spring Boot 4 Complete Guide dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Spring Boot 4 Complete Guide?

Tidak diperlukan pengalaman sebelumnya. Spring Boot 4 Complete Guide di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Kueri JPQL dan Native dengan @Query” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Spring Boot 4 Complete Guide ini?

Ya. Setiap pelajaran Spring Boot 4 Complete Guide menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Metode Kueri Turunan dan Resolusi Kata Kunci
  2. Kueri JPQL dan Native dengan @Query
  3. Spesifikasi dan Penyaringan Dinamis Berbasis Kriteria
  4. Paginasi, Pengurutan, dan Streaming Potongan
← Kembali ke Spring Boot 4 Complete Guide