openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pinaki Poddar <ppod...@apache.org>
Subject Re: Removal of unnecessary "Order By" clauses
Date Wed, 29 Feb 2012 20:06:57 GMT
> Extra performance cost that comes as a price for just wanting to use List
API. 
That is not a sound argument. 
Firstly, a performance cost is not a bug. 
Secondly, a feature i.e. to have List maintain order, it is natural that a
provider will need some code and code costs. But that cost can not be termed
as a performance cost. That is a feature cost.

With current capabilities of OpenJPA, a user determines and has complete
control on whether s/he wants Set or List to represent a domain model
properties.  If a user does use List API it means s/he requires ordering
semantics. And that declaration is sufficient for OpenJPA to maintain
element ordering for him/her. So what is the confusion about "just wanting
to use List API"?


-----
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context: http://openjpa.208410.n2.nabble.com/Removal-of-unnecessary-Order-By-clauses-tp7315925p7330537.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Mime
View raw message