Whoosh differentiates between "search by" and "display" values of the fields. By default, the same value is used for both cases, but when one needs to display different value (we allow searching for ticket id-s using ID and #ID syntax, but only show ID), one can add _stored_FIELDNAME to dict, and that value will be use when FIELDNAME is returned in document.
Anze On Thu, Jun 12, 2014 at 9:15 PM, Antonia Horincar <[email protected]> wrote: > Thank you for the info. I have no idea why it works on server either. > > My question now is regarding a ticket field created for indexing in Whoosh. > TicketIndexer has the method build_doc(trac_doc), which at one point creates > the field ‘_stored_name’, and assigns the ticket id as its value. What is the > role of this field? Because it isn’t specified in the Whoosh schema (and > neither in IndexFields and TicketFields). > > Thanks, > Antonia > > On 12 June 2014 at 09:15:47, Anže Starič ([email protected]) wrote: > > I have no idea why it works when it is run on server, but the infinite > recursion looks like a Babel problem. It is caused by deepcopy-ing a > LazyProxy object. I have managed to work around it by modifying > LazyProxy object in Babel [1]. > > > Anze > > [1] > https://github.com/astaric/babel/commit/53b38bfc7c06bb20d88897946affc9f28344db9f > > On Thu, Jun 12, 2014 at 3:12 AM, Antonia Horincar > <[email protected]> wrote: >> Thanks a lot for your help. TicketIndexer is really helpful for my issue. I >> noticed than I can’t initialise TicketIndexer in the Python interpreter (due >> to the same runtime error I mentioned earlier), but I can test it when >> running it on the server (through match_request and process_request), so >> that’s not a problem for now. >> >> Antonia
