annotate accounts/fixtures/accounts.json @ 943:cf9918328c64
Haystack tweaks for Django 1.7.7.
I had to upgrade to Haystack 2.3.1 to get it to work with Django
1.7.7. I also had to update the Xapian backend. But I ran into
problems.
On my laptop anyway (Ubuntu 14.0.4), xapian gets mad when search terms
are greater than 245 chars (or something) when indexing. So I created
a custom field that would simply omit terms greater than 64 chars and
used this field everywhere I previously used a CharField.
Secondly, the custom search form was broken now. Something changed in
the Xapian backend and exact searches stopped working. Fortunately the
auto_query (which I was using originally and broke during an upgrade)
started working again. So I cut the search form back over to doing an
auto_query. I kept the form the same (3 fields) because I didn't want
to change the form and I think it's better that way.
author |
Brian Neal <bgneal@gmail.com> |
date |
Wed, 13 May 2015 20:25:07 -0500 |
parents |
ee87ea74d46b |
children |
|
rev |
line source |
bgneal@236
|
1 [
|
bgneal@236
|
2 {
|
bgneal@236
|
3 "pk": 1,
|
bgneal@236
|
4 "model": "accounts.illegalusername",
|
bgneal@236
|
5 "fields": {
|
bgneal@236
|
6 "username": "root"
|
bgneal@236
|
7 }
|
bgneal@236
|
8 },
|
bgneal@236
|
9 {
|
bgneal@236
|
10 "pk": 2,
|
bgneal@236
|
11 "model": "accounts.illegalusername",
|
bgneal@236
|
12 "fields": {
|
bgneal@236
|
13 "username": "sg101"
|
bgneal@236
|
14 }
|
bgneal@236
|
15 },
|
bgneal@236
|
16 {
|
bgneal@236
|
17 "pk": 3,
|
bgneal@236
|
18 "model": "accounts.illegalusername",
|
bgneal@236
|
19 "fields": {
|
bgneal@236
|
20 "username": "surfguitar101"
|
bgneal@236
|
21 }
|
bgneal@236
|
22 },
|
bgneal@236
|
23 {
|
bgneal@236
|
24 "pk": 4,
|
bgneal@236
|
25 "model": "accounts.illegalusername",
|
bgneal@236
|
26 "fields": {
|
bgneal@236
|
27 "username": "webmaster"
|
bgneal@236
|
28 }
|
bgneal@236
|
29 }
|
bgneal@236
|
30 ] |