Comments on: Reindexing a single object using Django & Haystack http://slacy.com/blog/2009/11/reindexing-a-single-object-using-django-haystack/ This site is solar powered! Sat, 19 May 2012 03:18:15 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: slacy http://slacy.com/blog/2009/11/reindexing-a-single-object-using-django-haystack/comment-page-1/#comment-17884 slacy Thu, 19 Nov 2009 16:42:34 +0000 http://slacy.com/blog/?p=1006#comment-17884 Yeah, I know that saving the model will also update the index, I should have mentioned that my model has something akin to "last_modified=DateTimeField(auto_now=True)". So, I don't want to call save() on the model, because it would result in updating of the last_modified time, which is incorrect. Oh, and I'm not sure I buy your argument about "site". You have to remember that "http://localhost:8000/admin" is actually a "site". It includes models, views, etc. With Haystack, on the other hand, I like the symmetry with the admin interface, but I don't think of it as it's own "site". It's much more like a reusable app. I'd still prefer if it were called something like "engine". Just because you're modeling on the admin API doesn't mean you can't make some other changes here and there when they make sense. BTW, If SearhcIndex is becoming RealTimeSearchIndex, does that mean that there's a Non-realtime search index as well? What's the difference? I guess I should just read the source. :) Yeah, I know that saving the model will also update the index, I should have mentioned that my model has something akin to “last_modified=DateTimeField(auto_now=True)”. So, I don’t want to call save() on the model, because it would result in updating of the last_modified time, which is incorrect.

Oh, and I’m not sure I buy your argument about “site”. You have to remember that “http://localhost:8000/admin” is actually a “site”. It includes models, views, etc. With Haystack, on the other hand, I like the symmetry with the admin interface, but I don’t think of it as it’s own “site”. It’s much more like a reusable app. I’d still prefer if it were called something like “engine”. Just because you’re modeling on the admin API doesn’t mean you can’t make some other changes here and there when they make sense.

BTW, If SearhcIndex is becoming RealTimeSearchIndex, does that mean that there’s a Non-realtime search index as well? What’s the difference? I guess I should just read the source. :)

]]> By: Daniel Lindsley http://slacy.com/blog/2009/11/reindexing-a-single-object-using-django-haystack/comment-page-1/#comment-17883 Daniel Lindsley Thu, 19 Nov 2009 03:38:34 +0000 http://slacy.com/blog/?p=1006#comment-17883 If you're using the standard ``SearchIndex`` (soon to become ``RealTimeSearchIndex``), just saving the model in question will update the document in the index. If not, your code is correct. As for ``site``, it really refers to a customized registry of models available for the site it serves. It was also chosen because it was consistent with ``admin.site.register(Model, ModelAdmin)``, so that most users would find it more familiar. And care was taken to namespace to the ``haystack`` module to prevent collisions with other objects. If you’re using the standard “SearchIndex“ (soon to become “RealTimeSearchIndex“), just saving the model in question will update the document in the index. If not, your code is correct.

As for “site“, it really refers to a customized registry of models available for the site it serves. It was also chosen because it was consistent with “admin.site.register(Model, ModelAdmin)“, so that most users would find it more familiar. And care was taken to namespace to the “haystack“ module to prevent collisions with other objects.

]]>