StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20698236
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
8
CommunityOwnedDate
CreationDate
2013-12-20T07:12:35.760
FavoriteCount
0
LastActivityDate
2013-12-20T07:12:35.760
LastEditDate
LastEditorUserId
0
OwnerUserId
1196339
ParentId
16144017
PostTypeId
2
Score
36
ViewCount
0
LastEditorDisplayName
text
Body
@abject_error 's answer using <code>$timeout</code> does work. I edited your fiddle with his suggestion and made this <a href="http://jsfiddle.net/nackjicholson/5p6vF/2/">jsFiddle</a> CAVEAT I think the solution is indicative of a bigger problem in the form of a race condition! <h1><a href="http://jsfiddle.net/nackjicholson/5p6vF/">jsFiddle using filterFilter and $watch</a></h1> and that fiddle is the way around it for reals. And here is the explanation Your race condition is between handling the change of <code>search</code> and the availability of <code>$scope.filtered</code>. I think the culprits to eliminate in order to resolve this race condition are: <pre><code>ng-model="search" ng-change="filter()" </code></pre> and <pre><code>ng-repeat="data in filtered = (list | filter:search)......." </code></pre> Using <code>ng-change</code> to fire off "filter()" to do the calculation of <code>noOfPages</code> but also depending on a change in search in order to create <code>filtered</code>. Doing it this way, ensures the filtered list cannot possibly be ready in time to calculate the number of pages, and that's why hobbling "filter()" by 10ms with a timeout gives you the illusion of a working program. What you need is a way to "watch" <code>search</code> for changes, and then filter the list in a place where you have access to both creating <code>$scope.filtered</code> and calculating <code>$scope.noOfPages</code>. All in sequence, without a race. Angular has that way! It is possible to use the <code>filter</code> filter in your controller as function very poorly named: <code>filterFilter</code>. Check this out in the <a href="http://docs.angularjs.org/guide/filter">Filters Guide - Using filters in controllers and services</a> Inject it into the controller. <pre><code>function pageCtrl($scope, filterFilter) { // ... } </code></pre> Use it in a <code>$watch</code> function, documented in the <a href="http://docs.angularjs.org/api/ng.%24rootScope.Scope">scopes docs</a> <pre><code>$scope.$watch('search', function(term) { // Create filtered $scope.filtered = filterFilter($scope.list, term); // Then calculate noOfPages $scope.noOfPages = Math.ceil($scope.filtered.length/$scope.entryLimit); }) </code></pre> Change the template to reflect our new way. No more in DOM filter, or <code>ng-change</code> <pre><code><input type="text" ng-model="search" placeholder="Search"/> </code></pre> and <pre><code><li ng-repeat="data in filtered | startFrom:(currentPage-1)*entryLimit | limitTo:entryLimit"> {{data.name}} </li> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUpdate pagination in AngularJS after filtering
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnackjicholson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.