From: Markus KARG <markus.karg_at_gmx.net>
Date: Tue, 15 Apr 2008 19:33:13 +0200

I see! Thank you for this interesting point.

Regards
Markus

James Sutherland schrieb:
> The setting of some query hints or query properties on the named query after
> accessing it from the entity manager can require the query's SQL to be
> regenerated (hints that affect the SQL). For named queries it is best to
> set all of the hints on the original named query definition.
>
>
> Markus KARG-2 wrote:
>
>> James,
>>
>> thank you very much for that detailed explanation. Now I see clear. My
>> test (like virtually any micro benchmark) was not good enough. I will
>> follow your tips to do more (and better) performance measuring when the
>> application is finished. :-)
>>
>> You talked about the possibility of modifying the named query? What do
>> you mean with "modifying"?
>>
>>
>
>
> -----
> ---
> http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland
> http://www.eclipse.org/eclipselink/
> EclipseLink , http://www.oracle.com/technology/products/ias/toplink/
> TopLink
> Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink ,
> http://wiki.oracle.com/page/TopLink TopLink
> Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink ,
> http://www.nabble.com/EclipseLink-f26430.html EclipseLink
> Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence
>

-- 
http://www.xing.com/go/invita/58469