[Feature] Show Table page size for server side pagination

[hetunandu]

Summary

We don't show any information about row count on the table for server side pagination.

Motivation

Need to understand that we have reached the end of results

Additional Context

For server side pagination, we do not show any record info

For client side we show this

[Nikhil-Nandagopal]

@hetunandu we don't do this because this is the total number of records in the table not just the records on the first page. In serverside pagination this information doesn't make sense

[notacouch]

@Nikhil-Nandagopal Right now there is no way to know how many records are even being displayed. If the table can show 100 records, but the query only returned 99 for this page, we have no way of knowing. If this page returned 100, we know there's a chance there's another page. But if we have no idea of the records being shown, we don't know whether to paginate or not or if we missed to scroll down, nothing. I don't want to make a made up column as part of my queries just to show this.

[Nikhil-Nandagopal]

@notacouch to understand your request correctly, you are looking for a feature to see the number of records per page because you want users to know whether they should go to the next page or not. Is this correct?

Today we show the total number of records in the table rather than records per page because most tables with multiple pages will show the same information except for the last page.
To solve your problem, do you think it would be more useful for us to allow you to configure a total number of pages property that will automatically disable the next/previous button if the last page is reached?

As a workaround for now Instead of another column, you could use a text widget and bind it to Records: {{Table1.tableData.length}} to show this information

[notacouch]

@Nikhil-Nandagopal Good questions.

Today we show the total number of records in the table rather ...

By this do you mean the property you later mentioned, i.e. {{Table1.tableData.length}}?

To solve your problem, do you think it would be more useful for us to allow you to configure a total number of pages property that will automatically disable the next/previous button if the last page is reached?

That's quite alright, because for server side pagination if we're limiting the query and with an offset, we won't know the actual total number of results/pages (I guess unless we provide that via separate query just for counting).

It would be nice to display just the number of records in table as done with clientside instead of having to show this elsewhere. But it's good to know there is a property I can use. What I can do is adjust the layout, put a container beside the table to show details and actions.

Thanks for the workaround suggestion!

[Nikhil-Nandagopal]

@notacouch so then maybe a feature to mention the number of records / page. If fewer records than what is configured are returned, we can disable the next page button

[notacouch]

@Nikhil-Nandagopal That sounds like a pretty good idea, thank you!

[Nikhil-Nandagopal]

Closing this in favor of #2230