RE: dataTable - Millions of records

[Joshua Davis]

I just connect my data table / data scroller up to a backing bean fed by a Hibernate-based DAO.   The sorting in the <x:commandSortHeader> generates the 'order by' in the Hibernate query.   The data scroller information is fed to the DAO as well, which informs the result set handling (set first result, etc.).   The selection is handled by a session scoped form which is edited on a different page.  Honestly, I use Hibernate in part because I can't be bothered to figure out all the peculiarities of each database.   I suppose I'm just lazy like that.  ;)   BTW, the <x:dataTable preserveDataModel="true"> feature works great! From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 09, 2005 9:45 PM To: users@myfaces.apache.org; users@myfaces.apache.org Subject: RE: dataTable - Millions of records I totally see the purpose of coding the SQL so that you would get only a subset of the data at a time (Oracle gives what you pointed out. SQL Server, as far as i know does not offer such functionality out of the box) . However, once you throw sorting data in the game, isn't it much more complicated to handle and might actually make you run more queries than required if you deal with the subset/ordering in your backing bean?   I'm not actually sure here, I'm just wondering how you would handle sorting and using subsets in that case... It's an interesting dicussion though as many people are either going through this, or will go through it when developping their applications.   Greg -----Original Message----- From: David Haynes [mailto:[EMAIL PROTECTED] Sent: Fri 9/9/2005 8:32 PM To: MyFaces Discussion Cc: Subject: Re: dataTable - Millions of records