[master] Jakarta Persistence 3.2 new feature - JPQL UNION, INTERSECT, EXCEPT, CAST #1937
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change doesn't create anything new as specified operators/functions were already specified as a part of EclipseLink JPQL extensions from 2.4 version.
There is refactoring/movement of affected code related with
org.eclipse.persistence.jpa.jpql.parser.CastExpression
,org.eclipse.persistence.jpa.jpql.parser.DatabaseType
,org.eclipse.persistence.jpa.jpql.parser.UnionClause
fromEclipseLink...
classes to default JPQL classes.Due this movement all specified operators/functions are available from Jakarta Persistence/JPQL Grammar 3.2.
EclipseLink issue is described at #1885 and Jakarta Persistence specification request at the jakartaee/persistence#395 (cast) and jakartaee/persistence#398 (union, intersect, and except)