[Xapian-tickets] [Xapian] #414: QueryParser corner cases

[Xapian]

#414: QueryParser corner cases
-------------------------+--------------------------
 Reporter:  olly         |             Owner:  olly
     Type:  defect       |            Status:  new
 Priority:  normal       |         Milestone:  1.3.x
Component:  QueryParser  |           Version:
 Severity:  normal       |        Resolution:
 Keywords:               |        Blocked By:
 Blocking:               |  Operating System:  All
-------------------------+--------------------------
\
\
\
\
\
\
Description changed by olly:
\

Old description:

> There are quite a few cases which we probably don't handle as well as we
> could (sometimes it's not totally clear what the behaviour should be), so
> let's make a list here and see if we can find resolutions, or decide the
> current behaviour is fine.
>
> With FLAG_SYNONYM these cause reparsing so parse as {{{foo abc def}}} (we
> just ignore ~ unless the next character is a word character, so without
> the "foo:" prefix, ~ is just ignored):
>
> {{{
> ~foo:(abc def)
> ~foo:"abc def"
> }}}

New description:

 There are quite a few cases which we probably don't handle as well as we
 could (sometimes it's not totally clear what the behaviour should be), so
 let's make a list here and see if we can find resolutions, or decide the
 current behaviour is fine.

 With FLAG_SYNONYM these cause reparsing so parse as {{{foo abc def}}} (we
 just ignore ~ unless the next character is a word character, so without
 the "foo:" prefix, ~ is just ignored):

 {{{
 ~foo:(abc def)
 ~foo:"abc def"
 }}}

 Assuming "foo" is set as a non-boolean prefix, the first should probably
 parse as synonyms for the two terms, so the same as:

 {{{
 ~foo:abc ~foo:def
 }}}

 And the second should probably do a multi-word synonym expansion.

--
\
\
\
\

--
Ticket URL: <http://trac.xapian.org/ticket/414#comment:3>
Xapian <http://xapian.org/>
Xapian