difference from django-completion #2

coleifer opened this Issue Jun 7, 2012 · 2 comments


None yet
2 participants

coleifer commented Jun 7, 2012

Hi, I'm the author of a similar project django-completion (I see you have a fork of it in your projects list)! I was wondering if there were any big differences in our implementations?


ara818 commented Jun 7, 2012

I started by forking your project...Then i realized that the solr part was much more heavily developed and I was more interested in the redis aspect of it, and since the site this is being used on had heavy and complex autocompleting needs, I decided to create a new project using yours as inspiration. Over the past year or two it has diverged quite a bit...

Other than the obvious fact that it is redis only it:

  • Allows multiple autocompleters per install, each using any combination of different models as data sources.
  • Allow a single model to match on more than one term, ie for stocks autocomplete against "Apple" and "AAPL"
  • Support out of order word matching when one contiguous phrase does not match.
  • Supports a maximum number of contiguos words it will store per object.
  • Is higher performance at least on redis, using pipelining.
  • Has a specialized way of adding or removing all the objects in the autocompleter at once.
  • Has a management command to load and remove autocompleter items en masse.
  • Has a concept of exact matches and can move exact matches to be the first result.
  • Has a concept of score to allow for user specified ordering of matches....

That's what I can remember off the top of my head....I should say I'm actually in the process of massively rewriting this right now to meet our future needs, so it's due to change more from what's already there.

@ara818 ara818 closed this Jun 7, 2012

coleifer commented Jun 7, 2012

Wow, awesome, sound like lots of good features. Just curious!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment