You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Eric Everman <ev...@precedadesign.com> on 2005/01/03 17:41:23 UTC
contrib:Table with large datasets
Hi-
I'm wondering if anyone has suggestions for using contrib:Table with
large datasets (100k or more). It looks like the Table wants to read
in all row data even when it is only displaying a small portion of it,
which quickly results in OutOfMemoryError's.
I'm using Hibernate for persistence, though in this case the table data
is not editable and I could easily use a straight JDBC query.
Conceptually I think I would need to incorporate the current page
number and page size into the query so that only appropriate rows are
returned, yet maintain the illusion of the 100k rows to the Table
component so it can maintain paging state. Any ideas? Has this been
done before?
Thanks,
Eric Everman
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: contrib:Table with large datasets
Posted by Michael Henderson <mh...@mac.com>.
Hi,
I'm not sure if Hibernate has this feature but Cayenne allows you to
perform 'paged' queries. In essence only the primary key fields are
fetched and a custom
collection/list returned that fills in pages (you specify page size) of
objects as you iterate over the collection.
From my WO/EOF days I remember that this type of query was always
painful because of the time taken to instantiate all of the objects in a
large result set. I always used 'raw row' fetches for this type of thing
(closer to JDBC than ORM). Perhaps the Cayenne method fixes this?
Cheers,
Mike
Erik Hatcher wrote:
> Implement your own IBasicTableModel and hook it into the source of
> your contrib:Table
>
> Erik
>
> On Jan 3, 2005, at 11:41 AM, Eric Everman wrote:
>
>> Hi-
>>
>> I'm wondering if anyone has suggestions for using contrib:Table with
>> large datasets (100k or more). It looks like the Table wants to read
>> in all row data even when it is only displaying a small portion of
>> it, which quickly results in OutOfMemoryError's.
>>
>> I'm using Hibernate for persistence, though in this case the table
>> data is not editable and I could easily use a straight JDBC query.
>> Conceptually I think I would need to incorporate the current page
>> number and page size into the query so that only appropriate rows are
>> returned, yet maintain the illusion of the 100k rows to the Table
>> component so it can maintain paging state. Any ideas? Has this been
>> done before?
>>
>> Thanks,
>> Eric Everman
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: contrib:Table with large datasets
Posted by Eric Everman <ev...@precedadesign.com>.
Thanks Erik- that did the trick.
Eric E.
On Jan 3, 2005, at 11:06 AM, Erik Hatcher wrote:
> Implement your own IBasicTableModel and hook it into the source of
> your contrib:Table
>
> Erik
>
> On Jan 3, 2005, at 11:41 AM, Eric Everman wrote:
>
>> Hi-
>>
>> I'm wondering if anyone has suggestions for using contrib:Table with
>> large datasets (100k or more). It looks like the Table wants to read
>> in all row data even when it is only displaying a small portion of
>> it, which quickly results in OutOfMemoryError's.
>>
>> I'm using Hibernate for persistence, though in this case the table
>> data is not editable and I could easily use a straight JDBC query.
>> Conceptually I think I would need to incorporate the current page
>> number and page size into the query so that only appropriate rows are
>> returned, yet maintain the illusion of the 100k rows to the Table
>> component so it can maintain paging state. Any ideas? Has this been
>> done before?
>>
>> Thanks,
>> Eric Everman
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: contrib:Table with large datasets
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
Implement your own IBasicTableModel and hook it into the source of your
contrib:Table
Erik
On Jan 3, 2005, at 11:41 AM, Eric Everman wrote:
> Hi-
>
> I'm wondering if anyone has suggestions for using contrib:Table with
> large datasets (100k or more). It looks like the Table wants to read
> in all row data even when it is only displaying a small portion of it,
> which quickly results in OutOfMemoryError's.
>
> I'm using Hibernate for persistence, though in this case the table
> data is not editable and I could easily use a straight JDBC query.
> Conceptually I think I would need to incorporate the current page
> number and page size into the query so that only appropriate rows are
> returned, yet maintain the illusion of the 100k rows to the Table
> component so it can maintain paging state. Any ideas? Has this been
> done before?
>
> Thanks,
> Eric Everman
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org