Re: Full text indexing in small site

I want to make an app, that is independent of the DB system so it would be better to use some outer fulltext index -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To

Re: Full text indexing in small site

On Sun, Dec 26, 2010 at 11:06 AM, robos85 wrote: > Hi, > what engine fo fulltext indexing do you recommend? Small will be rather > small, about 3000-4000 unique users per day. I need to index content of > articles. It's avarage about 600-800 words. > If you are using MySQL,

Re: Full text indexing in small site

Have a look at haystack [1]. What engine you use pretty much depends on what you can install, for your small site even whoosh should be enough. Jonas [1] http://haystacksearch.org/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to

Full text indexing in small site

Hi, what engine fo fulltext indexing do you recommend? Small will be rather small, about 3000-4000 unique users per day. I need to index content of articles. It's avarage about 600-800 words. Thanks for advice -- You received this message because you are subscribed to the Google Groups

Re: full-text indexing

There was a very impressive demonstration of SOLR at OSCON this year, and it looks very, very easy to set up for light(i.e. reasonable but not-heavy) usage. The default install comes pretty much ready to roll - you'll have to tweak out a "schema" description of what you're indexing, and work on a

Re: full-text indexing

Jarek Zgoda wrote: > I don't know what do you mean by "transactions" in case of full-text > search engine as it doesn't do any multi-step updates (only single- > step deletes or inserts in case of PyLucene). > > Anybody who wants to use PyLucene, be aware that you cann't embed (iow > "use",

Re: full-text indexing

I don't know what do you mean by "transactions" in case of full-text search engine as it doesn't do any multi-step updates (only single- step deletes or inserts in case of PyLucene). Anybody who wants to use PyLucene, be aware that you cann't embed (iow "use", "import") PyLucene in your Django

Re: full-text indexing

Hi Thomas, On 8/7/07, Thomas Guettler <[EMAIL PROTECTED]> wrote: > > Am Dienstag, 7. August 2007 12:02 schrieb Kai Kuehne: > > http://www.rkblog.rk.edu.pl/w/p/django-lupy/ > > Hi, > > Does lupy support transactions? Do both (SQL und text database) > syncronize their transactions (commit or

Re: full-text indexing

Am Dienstag, 7. August 2007 12:02 schrieb Kai Kuehne: > http://www.rkblog.rk.edu.pl/w/p/django-lupy/ Hi, Does lupy support transactions? Do both (SQL und text database) syncronize their transactions (commit or rollback both)? Thomas --~--~-~--~~~---~--~~ You

Re: full-text indexing

http://www.rkblog.rk.edu.pl/w/p/django-lupy/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group,

Re: full-text indexing

On 8/7/07, cesco <[EMAIL PROTECTED]> wrote: > > Hi, > > is there any rough estimate on when the full-text indexing branch will > be integrated into trunk? The short answer is that there isn't really a rough estimate for anything on Django - and especially not on branch me

Re: full-text indexing

On Aug 6, 7:47 pm, cesco <[EMAIL PROTECTED]> wrote: > Hi, > > is there any rough estimate on when the full-text indexing branch will > be integrated into trunk? You can already use full text indexing in Django with the excellent Sphinx search engine [1]. There's some code on

Re: full-text indexing

I think that full text search works with mysql and with a patched version for postgresql [1] (prefered way!) But this is not my prefered way to use full text search I think, because: 1. no ranking by revelance support (at least for postgres) 2. most of the time you want to search throught a model

Re: full-text indexing

On 6 Sie, 19:47, cesco <[EMAIL PROTECTED]> wrote: > is there any rough estimate on when the full-text indexing branch will > be integrated into trunk? Well, at least PyLucene full-text search code is unusable in current form found in this branch. Any threading GCJ-compi

full-text indexing

Hi, is there any rough estimate on when the full-text indexing branch will be integrated into trunk? Thanks Francesco --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to