Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ember-data RESTAdapter pagination and filtering #1059

Closed
kwladyka opened this issue Jun 29, 2013 · 4 comments
Closed

ember-data RESTAdapter pagination and filtering #1059

kwladyka opened this issue Jun 29, 2013 · 4 comments

Comments

@kwladyka
Copy link

Hi,

In my opinion ember strongly need one additional solution. I talked about that with some people and also looking in the internet. The problem is recurrent.

Table like on that image:
ember table

http://i.stack.imgur.com/R1BRg.png

On the top is filter row.

Using http://emberjs.com/guides/models/the-rest-adapter/

Problem nr 1:
Imagine it is table with all users in system. Imagine it is about 100000 users in system. In that case ember have to download all users from server. Unsense. Additional pagination parameter is necessary. If pagination is set to 30 rows it will download only 30 rows user then. If user click other page, it will donwload other 30 rows. So i propose add parametter pagination to Find All DS.RESTAdapter. It can be solve in other way ofcourse. The most important is solution.

Problem nr 2:
Because of pagination If user fill filter field with some value it has to send query to server and download new data. It also need soltion.

Problem nr 3:
When user multiselect rows and click action "change status to blocked" selected rows have to read, query send and table refresh. I guess the best soltuion for that is code that in jquery,

I am not sure what is the best technical way in ember to solve that. I only know it is really important. Without that i cant really use ember to advenced software coding.

@OpakAlex
Copy link

+1

1 similar comment
@pbombo
Copy link

pbombo commented Aug 1, 2013

+1

@wagenet
Copy link
Member

wagenet commented Aug 13, 2013

Unfortunately, pagination adds more complexity than one might think at first. What if a record is deleted on the server or a new one is added that affects the already loaded pages? I definitely understand the interest here, but I'd love to see someone start a discussion on the forums so we can consider all the different cases we need to address. Once we have a proposal we're happy with we can reopen the issue here.

@wagenet wagenet closed this as completed Aug 13, 2013
@GetContented
Copy link

I wonder if #1517 needs more support behind it around this. Is this the same issue? i think so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants