-
-
Good fix though separate change :) I encountered this too.. I think we should probably just be setting reviewboard:url to a path without the http://, but we should protect against it here anyway.
-
-
-
-
-
-
What happens if get_full_name doesn't return anything but an empty string? Will it get mad if there's nothing there?
-
This function is so generic (aside from the "ReviewRequest") that I think this could be in its own app somewhere, maybe even in djblets. The search function could take an initial queryset so that it knows the object type, and then filter off that. I'd sure love to use this in other projects :)
-
-
-
Not sure we should assume there's a full name. In one of the other templates, we call something that gives us the proper display name (full name if possible, falling back on username).
Add search
Review Request #200 — Created Jan. 2, 2008 and submitted
This is an initial stab at fulltext and field-specific search. It uses PyLucene/JCC, which calls into the apache lucene implementation through the JNI. The indexing is done via a manage.py command "index" which can do either a full or incremental index of the database. There's still a few things left before this is perfect. I need to figure out: 1. Review indexing. I'm blocked on the fact that I can't import reviews now due to that bug that's being discussed on the list. 2. Filename indexing needs a better tokenizer. I'll probably have to tokenize it myself. 3. It doesn't index dates yet. 4. This needs to be documented a lot -- especially how to build PyLucene, which is a total pain.
Used it a lot! It's sweet!