Community
Participate
Working Groups
Build Identifier: 2.2.1 It would be valuable to have a query hint which says that an attribute should not be loaded at all. Independent of the underlying configuration (which is as it is maybe for other reasons), it would then be possible to switch of fetching for the configured attribute. Reproducible: Always
I have implemented this in my patched version of EclipseLink. If there is interest, I would happily supply a patch. best regards, Martin
closing. the way to do this is through our fetch group support. http://wiki.eclipse.org/EclipseLink/Examples/JPA/AttributeGroup
Hi Tom, I think you have closed this a bit fast. I have of course seen and evaluated your fetch group support - but if I have an entity with 25 attributes, it seems a bit tedious to write such a Fetch Group for each and every possibility of what and how I want to query - in some cases I want to get everything _but_ this one relationship or attribute? In any case I have realized during implementation of this that your query information state handling makes stuff more complex than I would have thought. May I ask you how (from an eclipselink architect's perspective) hint information should be passed down to subqueries? Is there information on this available somewhere? Those subqueries are often re-used across main query executions, and I guess the hints should be there only for one execution. I have implemented my own QueryExecutionContext which is valid only for one QueryExecution now. Do you somehow pass something like this down the method invocaton chain and I haven't seen it? best regards, Martin
Reopening. A hint like the one suggested could be backed by a fetch group, but allow a simpler configuration strategy. Community. Please vote for this if you find it useful. Our query hints are not specifically passed to subqueries. Instead, what a hint does is set particular settings on a Query Object. Those settings are potentially available to subqueries if required. The way those settings would typically be made available to subqueries is during the process of building the SQL for the query and the subquery, we process the selection criteria (including the subquery) and build the subquery with any required settings.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
