|
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
|
- RE: dataTable - Millions of records gvial
- RE: dataTable - Millions of records Joshua Davis
- RE: dataTable - Millions of records Dave
- RE: dataTable - Millions of records Joshua Davis
- RE: dataTable - Millions of records Dave
- RE: dataTable - Millions of records Joshua Davis
- Re: dataTable - Millions of records David Haynes
- Re: dataTable - Millions of records Dave
- RE: dataTable - Millions of records Joshua Davis
- Re: dataTable - Millions of records Werner Punz

