Re: dataTable - Millions of records

[Dave]

Normally we have filters to select a portion of data from database table. But it can be very large too. For example, searching found 10,000 items. For the backend, ResultSet will have the 10,000 records. I am trying to understand how the ResultSet manages the 10,000 records. It would consume lots of memory if all of them in memory. For dataTable scroller, I still need to provide value binding for the whole set of data.

Kevin Galligan <[EMAIL PROTECTED]> wrote:

Out of curiosity, how are you planning to use the millions of rows? I
would assume you'd want to filter them in some way rather than attempt
to display them, right? That would kind of answer your question (your
datatable would only have the filtered results. Not the full table).

Mike Kienenberger wrote:
> Data fetching would depend on your backing Collection.
>
> You can use t:dataScroller to limit the dataTable to accessing only a
> subset of the data.
>
> I'd love to see a t:liveGridDataTable component like what's available
> at this site, but I suspect it's currently outside of my ability to
> implement.
>
> http://openrico.org/rico/livegrid.page
>
> On 9/8/05, Dave <[EMAIL PROTECTED]>wrote:
>
>>For a large database table that has millions of records(rows), how is the
>>memory managed from backend to ? all the millions of records
>>are in memory? That would crash the system. Is the collection( returned from
>>database layer) actually not filled with data until they are requested ?
>>Thanks. Dave
>>
>>__________________________________________________
>>Do You Yahoo!?
>>Tired of spam? Yahoo! Mail has the best spam protection around
>>http://mail.yahoo.com

---

Click here to donate to the Hurricane Katrina relief effort.