Thank you for all the answers! Given that I am implementing this for a demo purpose, I do not care about performances. I think I am going to do the 2 queries approach for the demo, then I would use a FTS engine in the future.
Thanks a lot Carlo Il giorno martedì 21 febbraio 2017 02:09:46 UTC+1, Shawn Milochik ha scritto: > > If you want a pre-rolled solution, just use Django-haystack. It'll do > exactly what you want. > > If you want to create your own to avoid the dependency on additional > libraries and backend (you'll need something like Elasticsearch), that's > easy also. Let me know if you do. I have some sample code lying around and > will dig it up and document it a bit if you're interested in implementing > it. You'll still need to have to store your own indexed data in some kind > of backend, but you can use whatever you like. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c1e0b295-4008-4cc3-8ca9-63bebe2395f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
