Hibernate ORM with Panache

• Active record (PanacheEntity) vs PanacheRepository — when to use each
• Parameterized HQL / Panache queries: positional (?1) and named (:param) — no unsafe concatenation
• @NamedQuery on entities for reusable, build-time validated queries
• DTO projections with project(Class) to avoid exposing managed entities
• Pagination with Page.of(pageIndex, pageSize) and query.count()
• N+1 avoidance with JOIN FETCH in HQL queries
• Optimistic locking with @Version and handling OptimisticLockException
• @Transactional application services
• @TestTransaction for automatic rollback in @QuarkusTest tests
• Mapping entities vs exposing DTOs at REST boundaries
• Pairing with

  @411

  for raw SQL when needed

Constraints

• MANDATORY: Run

  ./mvnw compile

  or

  mvn compile

  before applying any change
• PREREQUISITE: Project must compile before applying Panache improvements
• SAFETY: If compilation fails, stop immediately
• BLOCKING CONDITION: Compilation errors must be resolved by the user before proceeding
• VERIFY: Run

  ./mvnw clean verify

  or

  mvn clean verify

  after applying improvements
• BEFORE APPLYING: Read the reference for detailed rules and examples

When to use this skill

• Review Panache entities or repositories in Quarkus
• Improve Hibernate ORM data access with Panache
• Add DTO projections, JOIN FETCH, pagination, or optimistic locking to Panache queries
• Fix N+1 query problems or add @Version concurrency control in Quarkus Panache

Reference