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

force totalCount to be FALSE #209

Closed

Conversation

np25071984
Copy link
Contributor

Q A
Is bugfix? yes
New feature? no
Breaks BC? no
Tests pass? yes
Fixed issues #206, #201

One more way to fix the issues. In my opinion @grozzzny offer the best solution, due to we don't need change BaseDataProvider::_pagination scope.

@machour machour changed the title force totalCoutn to be FALSE force totalCount to be FALSE Jan 28, 2019
@samdark samdark added this to the 2.0.6 milestone Jan 29, 2019
Copy link
Member

@samdark samdark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need a line for the changelog.

{
/** `totalCount` is calculated after the request */
if (!empty($config['pagination'])) {
$config['pagination']['totalCount'] = false;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be mentioned that obtaining count is a cheap operation in ElasticSearch so it makes sense to always calculate it.

@samdark samdark closed this Feb 22, 2019
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

Successfully merging this pull request may close these issues.

2 participants