users@glassfish.java.net

Re: JPA and Joins Returning too much information

From: <glassfish_at_javadesktop.org>
Date: Wed, 09 Jan 2008 11:56:45 PST

Thanks for the reply.
By setting the fetch type to lazy, i can see in the profiler that the claimline table is not accessed until needed, which will be good from a performance standpoint. We will use nested loops, one to get the member, and the second to get the member's claims that meet the date criteria. seems to work just fine.
[Message sent by forum member 'epenetar' (epenetar)]

http://forums.java.net/jive/thread.jspa?messageID=253054