$$index bug on server sierve-side paging
See original GitHub issueI’m submitting a … (check one with “x”)
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here
Current behavior Something changes $$index inside array for rows on server-side paging. On first load of page everything is ok, but when u return to it the order of rows changes.
Expected behavior The order of rows doesnt change on page change. Reproduction of the problem http://plnkr.co/edit/XXiJfDDKxLv3X7IT0QQa?p=preview
or server-paging in demos
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
-
Table version: 1.7.0
-
Angular version: 2.2.0
-
Browser: all
-
Language: TypeScript 2.1.1
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Server side paging should just work of rows without index #293
With server side paging data table expects data in index position relative to the page. For example for second page with page size...
Read more >bug with server-side pagination — DataTables forums
Hi, I'm using server-side processing and I can't set page like this: table.page(pageIndex).ajax.url('someUrl').load(function() ...
Read more >Creating an appropriate index for server-side paging query
Hey I did some testing with dummy data on my local. I am making this recommendations considering you do not have any index...
Read more >Bug with Data Action together with start index & pagination
with an aggregate in a screen, you give it a startindex, and the platform makes sure that underwater the correct set of records...
Read more >Optimising Server-Side Paging - Part I - SQLServerCentral
The problem is that SQL Server is fetching the off-index columns for every row it examines - not just the rows that will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The bug is fixed for me in 2.1.3, not sure in which version you’ve fixed it, but it works now
No, I haven’t took time to investigate, but it’s in the 1.6.0 release 😃