Closed CristopherH95 closed 3 years ago
Strangely enough, I have been unable to replicate the error reported in the build locally. I will have to dive deeper into this to fix the build error.
Hi,
Thank for this MR! It looks great, and I appreciate the test for the new feature. :)
If you can figure out the build error, I'd be very happy to merge this. I can't see anything obvious that would be causing it. Hopefully you're figure it out!
Build errors have been fixed! The issue was a bug in some versions of Django which generates invalid SQL when attempting to use Cast
. I added a function get_pk_output_field
which wraps some logic to avoid this error. This is the bug for reference: https://code.djangoproject.com/ticket/28371.
This is excellent, and thanks for chasing down the bug! I'll push out a new watson release next week.
Release 1.6.0 has landed :)
Hello! This contribution is meant to resolve #276. In order to accomplish this, the following is added:
_get_deleted_entries_for_model
which retrieves any search entries for which the original object no longer exists.cleanup_model_index
which deletes any search entries for which the original object no longer exists.buildwatson
management command.testBuildWatsonCommand
test case which targets the above behavior.