Home » Eclipse Projects » EclipseLink » EclipseLink throws JPQLException on using SELECT ... AS in a constructor expression
EclipseLink throws JPQLException on using SELECT ... AS in a constructor expression [message #1819241] |
Fri, 10 January 2020 11:50 |
Karsten Wutzke Messages: 124 Registered: July 2009 |
Senior Member |
|
|
Hello,
I ported a webapp to EclipseLink and on init of the queries the persistence provider fails on the query:
aused by: Exception [EclipseLink-0] (Eclipse Persistence Services - 2.7.5.v20191016-ea124dd158): org.eclipse.persistence.exceptions.JPQLException
Exception Description: Syntax error parsing [
SELECT NEW net.bbstats.dto.PlayerStatDto(
gl.playerId,
gl.seasonStartYear,
gl.lastName,
gl.firstName,
gl.incognito,
COUNT(DISTINCT gl.gameId) AS games,
SUM(CASE WHEN gl.hasPlayed = FALSE THEN 1 ELSE 0 END) AS gamesplayed,
SUM(CASE WHEN gl.starter = TRUE THEN 1 ELSE 0 END) AS gamesstarted,
SUM(gl.threePointersMade),
SUM(gl.freeThrowsMade),
SUM(gl.freeThrowsAttempted),
SUM(gl.personalFouls),
SUM(CASE WHEN gl.personalFouls >= 5 THEN 1 ELSE 0 END),
SUM(gl.points) AS points,
MAX(gl.points),
MIN(gl.points)
)
FROM GameLog gl
WHERE gl.roundId = :roundId AND gl.groupCode = :groupCode AND gl.rosterId IN :rosterIds
GROUP BY
gl.playerId,
gl.seasonStartYear,
gl.lastName,
gl.firstName,
gl.incognito
ORDER BY gamesstarted DESC, games DESC, points DESC, gl.lastName, gl.firstName
].
[140, 141] The constructor expression has two constructor items ('COUNT(DISTINCT gl.gameId)' and 'AS games') that are not separated by a comma.
[204, 205] The constructor expression has two constructor items ('SUM(CASE WHEN gl.hasPlayed = FALSE THEN 1 ELSE 0 END)' and 'AS gamesplayed') that are not separated by a comma.
[271, 272] The constructor expression has two constructor items ('SUM(CASE WHEN gl.starter = TRUE THEN 1 ELSE 0 END)' and 'AS gamesstarted') that are not separated by a comma.
[462, 463] The constructor expression has two constructor items ('SUM(gl.points)' and 'AS points') that are not separated by a comma.
[141, 149] The expression is invalid, which means it does not follow the JPQL grammar.
[205, 219] The expression is invalid, which means it does not follow the JPQL grammar.
[272, 287] The expression is invalid, which means it does not follow the JPQL grammar.
[463, 472] The expression is invalid, which means it does not follow the JPQL grammar.
at org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildException(HermesParser.java:157)
at org.eclipse.persistence.internal.jpa.jpql.HermesParser.validate(HermesParser.java:336)
at org.eclipse.persistence.internal.jpa.jpql.HermesParser.populateQueryImp(HermesParser.java:280)
at org.eclipse.persistence.internal.jpa.jpql.HermesParser.buildQuery(HermesParser.java:165)
at org.eclipse.persistence.internal.jpa.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:142)
at org.eclipse.persistence.internal.jpa.JPAQuery.processJPQLQuery(JPAQuery.java:225)
at org.eclipse.persistence.internal.jpa.JPAQuery.prepare(JPAQuery.java:186)
at org.eclipse.persistence.queries.DatabaseQuery.prepareInternal(DatabaseQuery.java:631)
at org.eclipse.persistence.internal.sessions.AbstractSession.processJPAQuery(AbstractSession.java:4502)
at org.eclipse.persistence.internal.sessions.AbstractSession.processJPAQueries(AbstractSession.java:4462)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:645)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:868)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:811)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:256)
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:772)
... 201 more
Is this expected behavior? I think it is not very clever to disallow `AS` in constructor expressions...
I have also posted a question on SO here:
https://stackoverflow.com/questions/59677453/eclipselink-throws-jpqlexception-on-using-select-as-in-a-constructor-express
I would very much appreciate if someone could have a look at this and state his/her opinion.
Is this a missing feature? Is it just normal behavior because JPA doesn't specify it?
Thanks
Karsten
[Updated on: Fri, 10 January 2020 11:59] Report message to a moderator
|
|
| | | | | |
Goto Forum:
Current Time: Tue Dec 03 20:30:06 GMT 2024
Powered by FUDForum. Page generated in 0.03662 seconds
|