DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-894
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Core

In-memory query result class processing doesn't allow for "alias.fieldName" when determining field name to use for setter

Created: 12/Aug/12 03:02 PM   Updated: 19/Aug/12 09:29 PM   Resolved: 12/Aug/12 03:03 PM
Component/s: Queries
Affects Version/s: None
Fix Version/s: 3.1.1

 Description  « Hide
If the user invokes a (JPQL) query like
SELECT T.firstName, T.lastName FROM MyClass T
and specifies a result class and it is to be processed in-memory, the in-memory result class handler just looks for "T.firstName", "T.lastName" in the list of fields! Should take the last part of the name

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 12/Aug/12 03:03 PM
SVN trunk fixes this for PrimaryExpressions