[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724602#action_12724602
]
Craig Russell commented on JDO-633:
-----------------------------------
Andy commented:
A List has an order (whether it is an "indexed" List, or
an "ordered" List (using JPA-style ordering criteria)). The user puts items
in the List and persists the List. The user then wants to grab element at
index 2. Storing the order in the datastore, in some way, is essential to
support (indexed) Lists, hence querying should be straightforward. Since JDO
doesn't define an ordering constraint, it is reasonable to assume that in JDO
a List is an "indexed" List, hence retains the users ordering.
As far as testing goes, surely all you need to do is persist an object with a
List with some elements in some order, and then do a query, assuming the same
order as they had at the moment of persistence. Where does DB-specific SQL
come into this ? surely that is the problem for the implementation.
> List.get(int) support in JDOQL is missing
> -----------------------------------------
>
> Key: JDO-633
> URL: https://issues.apache.org/jira/browse/JDO-633
> Project: JDO
> Issue Type: New Feature
> Components: specification, tck2
> Affects Versions: JDO 2 maintenance release 2
> Reporter: Timo Westkämper
>
> It would be nice to get List.get(int) into JDOQL, in other words access of
> indexed list elements.
> Querydsl has support for that and for consistency it would be nice if JDOQL
> supported it as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
