Re: [eclipselink-users] Native queries...disturbing behavior...bug?

[Christopher Delahunt <christopher.delahunt@xxxxxxxxxx>]

Using native queries to return entities cause problems when incomplete or manipulated data is returned because these entities then become managed entities.  So unless it is a refresh query, the entities will be loaded with only the results from the first query.  The dont cache and read-only options suggested in the link will prevent the query from returning managed entities.  You could also try the refresh query hint, or you could build the entities yourself from the data returned.  

Best Regards,
Chris

On 06/10/2010 6:56 PM, Laird Nelson wrote:

On Wed, Oct 6, 2010 at 6:47 PM, Laird Nelson <ljnelson@xxxxxxxxx> wrote:

Is there any sharing of results between native queries?  Any ideas on where to look here for pilot or EclipseLink error?

Am I perhaps running into this: http://old.nabble.com/Eclipselink-and-Oracle-Total-Recall---Caching-Problem-td22437811.html?

It is true that these queries of mine will (a) return the same kind of entity and (b) each run could return an entity that has a primary key used by the prior query.

That must be what's going on...something doesn't feel right though.  :-)

L

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users