Keep in mind that the grid is just supposed to be an easy way to generate a
table.
If it's not fit for your purpose, you can always generate your own table
without grid.
I have been hoping that this issue would make it up the priority list which
I think solves the issue of receiving both the availableRows and paged data
in one call by allowing you to store the availableRows value.
https://issues.apache.org/jira/browse/TAP5-902
Thanks,
Dustin
On Fri, Jan 17, 20
Hmm... Looks like your right. Sorry for the confusion.
getAvailableRows() is called before prepare.
On 17 Jan 2014 13:49, "George Christman" wrote:
> I wouldn't say it's premature optimization when I'm essentially performing
> two of the exact same free text queries, it's twice the work ;-) My c
man [mailto:gchrist...@cardaddy.com]
> Lähetetty: 17. tammikuuta 2014 15:49
> Vastaanottaja: Tapestry users
> Aihe: Re: How to use grid with large data sets.
>
> I wouldn't say it's premature optimization when I'm essentially performing
> two of the exact same free
I wouldn't say it's premature optimization when I'm essentially performing
two of the exact same free text queries, it's twice the work ;-) My company
is hosting our dev database remotely on awful hardware to help us to find
performance issues. They believe if we can make something fast on dev, it
If there's a concept in lucene that allows you to bring back the total
rowcount and a page of data in a single query then the GridDataSource
interface can support that.
On 16 January 2014 22:36, Lance Java wrote:
> One query is for the rowcount, the other is for the results (for a single
> page
One query is for the rowcount, the other is for the results (for a single
page).
The only way to do it with one query is to add an extra column to the
result set for the row count. This value will be exactly the same for every
row in the result set.
I personally don't see an issue with 2 queries..
I found the following documentation
http://wiki.apache.org/tapestry/Tapestry5HibernateGridDatasource2
However I'm still a little confused, I'm seeing two queries needed to get
this to work, one containing the filtered results to get the availableRow
count
and the second one to get the prepare fil
So I'm playing with the GridDateSource and was wondering how you are
suppose to get the filtered result count for availableRows()? With
hibernate search you get this count after the results have been filtered,
but the way the methods are called in GridDataSource, the availableRows
method is called
I guys, thanks for the help, I'm using hibernate-search with lucene.
On Thu, Jan 16, 2014 at 12:10 PM, Ville Virtanen <
ville.virta...@orientimport.fi> wrote:
> Hi,
>
> here is one example:
>
>
> http://jumpstart.doublenegative.com.au/jumpstart7/examples/tables/griddataso
> urces
>
> Ville
>
> -
On Thu, 16 Jan 2014 14:34:17 -0200, George Christman
wrote:
Hello, I'm wondering how to use the grid component with large data sets.
Implement a GridDataSource and pass it to the source parameter of Grid
instead of a List. If you're using tapestry-hibernate, there's
HibernateGridDataSou
Hello,
did you try to set the datasource parameter
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/grid/GridDataSource.html
have a look at this great sample
http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/griddatasources
Also
http://packtlib.packtpub.com/library/9781
12 matches
Mail list logo