Tawus wrote: > > Hi > > This is something you should have a look at > > http://docs.jboss.org/hibernate/core/3.3/reference/en/html/performance.html > <http://docs.jboss.org/hibernate/core/3.3/reference/en/html/performance.html> > As an example, in one of our projects we had basic audit fields like > creator > user and modifier user in every table. > > Each time a grid was displayed, because of Eager Fetching, user table rows > were fetched along with > the other table rows. We could not go for lazy loading as the creator and > modifier were to be displayed too > > >
Hi, Actually, for join queries, the pagination is not effective when you use the "fetch" syntax (even if you use the setMaxResult...). See here for more details : http://java.dzone.com/articles/hibernate-tuning-queries-using?page=0,2 A solution is to get the result in 2 times : get the paginated data without "fetching" , then get joined data from the previous list (using the "IN" syntax and taking into account the sorting in the 2 queries) Nourredine. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Grid-with-Scroll-synchronization-Customization-tp3317448p3322702.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
