-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thx for your clarification.
Russell Keith-Magee a écrit :
> Indexing a fields makes searches over that field faster. Slug fields
> are the very definition of a searchable, indexable field - the most
> common use case for a Slug is as part of a URL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
When I use a SlugField in a model,
an index for this field is create in postgres.
Why ?
(config : django 0.96 / postgresql )
A++ Xav.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Holsman a écrit :
> put you might want to look at Solr ( http://lucene.apache.org/solr/ )
> which wraps the lucene search engine in a HTTP server.
Thx. I will see that.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Norjee a écrit :
> I'm afraid your solution only works when using the development server,
> and even then when used in auto_reload mode.
You are in true.
> I think the easiest solution is to simply execute the functions
> interfacing with pylucene in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Solution found in pylucene-dev :
changed django/utils/autoreload.py
from:
import thread
to:
import PyLucene.PythonThread as thread
Norjee a écrit :
> Pylucene has some threading issues (read incompatibilities with python
> threads, it must be run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thx :)
Norjee a écrit :
> Pylucene has some threading issues (read incompatibilities with python
> threads, it must be run from either the main thread, or its own thread
> version).
>
> The solution is rather simple, use it in its own separte thread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
My probleme with search-api and lucene :
I make index and search with a script python test.py.
python manage.py shell < test.py
It's ok, and give me results.
But when I use this.
python manage.py runserver 8080 --verbosity=2
and add the first l
