-
Notifications
You must be signed in to change notification settings - Fork 316
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
Incorrect Total Count in Laravel Scout Pagination #824
Comments
@karakhanyans do you have any thoughts here? |
@driesvints will check this and get back with more info 👌 |
I will be happy to see this solved guys. Good luck! |
@karakhanyans any news here? |
I'll be working on this |
Hello, I encountered the same issue reported here. In my case, I was using a model with a ULID as the primary key but initially forgot to set protected $keyType = 'string'; in my model. After updating this setting, I can confirm that the pagination now works correctly. Here are the specifics of my development environment:
Apologies if this solution has already been mentioned. I hope this helps someone else experiencing the same problem. Thank you. |
Ping @jasonbosco |
@AbdullahFaqeir will be working on this going forward. |
Hi @Evenerik! Can you please dump the collection schema, and sample record in typesense and the same record in database. Below you can see a dump of my env showing a working fresh sample, I've seeded 10K users. User model settings.Search performed.Paginated search results. |
Scout Version
10.8.6
Scout Driver
Typesense
Laravel Version
10.48.3
PHP Version
8.3.0
Database Driver & Version
MySQL 8.0.36
SDK Version
No response
Meilisearch CLI Version
No response
Description
This is pretty much a reopening of @razvaniacob's issue, who has encountered the same problem I am currently facing. I won't go into too much detail since he described the bug perfectly well in his issue, but Scout's
LengthAwarePaginator
shows wrong total when using Typesense's engineSteps To Reproduce
See steps in #819
The text was updated successfully, but these errors were encountered: