Make identification variables and the `SELECT` clause in JPQL optional #3902

Closed

Parent:Upgrade to JPA 3.2

Closed

Make identification variables and the SELECT clause in JPQL optional#3902

Parent:#3673

Assignees

Labels

type: enhancement

Milestone

4.0 M4 (2025.1.0)

Member

Since JPA 3.2, identification variables and the SELECT clause in Jakarta Persistence QL are now optional.

added a parent issue

on May 28, 2025

Upgrade to JPA 3.2 #3673

self-assigned this

on May 28, 2025

added

type: enhancement

on May 28, 2025

added this to the 4.0 M4 (2025.1.0) milestone

on May 28, 2025

added 2 commits that reference this issue

on May 28, 2025

Make identification variables and the `SELECT` clause in JPQL optional.

Polishing.

mentioned this

on May 28, 2025

Make identification variables and the SELECT clause in JPQL optional #3903

closed this as completedin d9c102e

added a commit that references this issue

Polishing.

added a commit that references this issue

Make identification variables and the `SELECT` clause in JPQL optional.

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

mp911de

Labels

type: enhancement

Type

No type

Projects

No projects

Milestone

4.0 M4 (2025.1.0)No due date

Relationships

Parent issue
- Upgrade to JPA 3.2spring-projects/spring-data-jpa#3673

Development

Make identification variables and the `SELECT` clause in JPQL optionalspring-projects/spring-data-jpa

Participants