-
Notifications
You must be signed in to change notification settings - Fork 93
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
Accept string based primary keys #163
base: master
Are you sure you want to change the base?
Conversation
self.backend.update(UUIDBlogSearchIndex(), UUIDBlogEntry.objects.all()) | ||
|
||
self.assertEqual(pks(self.backend.search(xapian.Query(''))['results']), | ||
[1, 2, 3]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why isn't this ['uuid-1', 'uuid-2', 'uuid-3']
? I thought that the goal was to ensure PK is a string.
13c1e02
to
5ef599f
Compare
1 similar comment
I believe the PR is almost ready to merge. As far as I understood, right now this tests the indexation (changes to I believe that one final addition is to test the search interface, that is roughly present in
(see here for examples) This would check that a search by id in Xapian corresponds to a search by id in Django's ORM, as we would expect. You can also add your name to the credits in the README, as part of this commit. Other than that, the code is clean and explicit, and, for me, this is ready to merge. Thanks a lot @charles-vdulac for this! |
Added test for search text-based ids.
Hi @jorgecarleitao Sorry for this long delay. I just merge your PR and rebased the branch to make it up to date. |
Would it be possible to make this pull request as part of the next release ? |
[fixes issue #138 ]
[closes pr #157 ]