Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dali » Validating IN expression still incorrectly shown as error
Validating IN expression still incorrectly shown as error [message #1764475] Tue, 30 May 2017 11:35
Karsten Wutzke is currently offline Karsten WutzkeFriend
Messages: 115
Registered: July 2009
Senior Member
Hello,

I have the following JPQL query:

SELECT we 
FROM Whatever we
  JOIN we.trade trd
  JOIN we.whateverType wet
WHERE trd.partnerId = :partnerId AND we.whateverType.id IN :whateverTypeIds
ORDER BY we.whateverType.id

This shows whatevers for the current partner and only the types of whatevers passed into the query via :whateverTypeIds, which is a list of integers (List<Integer>).

Now Dali shows two validation errors:

* The left parenthesis is missing from the IN expression. (red marker under the N of the IN keyword)
* The right parenthesis is missing from the IN expression. (red marker under the last s of the query param :whateverTypeIds)

I've already reported this problem several years ago here:

https://www.eclipse.org/forums/index.php/t/369011/

There's an answer by Pascal Filion: https://www.eclipse.org/forums/index.php?t=msg&th=369011&goto=900408&#msg_900408

... listing the following bug as being fixed:
2: Incorrect validation for IN expression using an input parameter
This should have been fixed in Indigo SR2 (3.7.2), see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=367593

However, this bug is *NOT* fixed in the latest Neon release I have downloaded a week ago (somewhere around 25th of May 2017).

Switching off the Dali validation is tough. Our project has so many badly named identifiers in queries because the entities were generated from the DB and we're successively refactoring them to usable fields, getters and setters.

Unfortunately Dali IN expression validation and bad identifiers are BOTH treated under the check box "Invalid or incomplete JPQL queries" instead of "Identifier not found" and "Bad expression"...

Can anyone please comment on this? What to do? Someone reopen the ticket?

Karsten
Previous Topic:JPA Diagram massive error
Next Topic:Can't create connection to SQL Server
Goto Forum:
  


Current Time: Fri Jun 22 15:18:41 GMT 2018

Powered by FUDForum. Page generated in 0.01507 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top