[Xapian-tickets] [Xapian] #697: Omega SORTREVERSE semantics confusing

[Xapian]

#697: Omega SORTREVERSE semantics confusing
--------------------+---------------------------
 Reporter:  olly    |             Owner:  olly
     Type:  defect  |            Status:  closed
 Priority:  normal  |         Milestone:  1.3.5
Component:  Omega   |           Version:  1.3.3
 Severity:  normal  |        Resolution:  fixed
 Keywords:          |        Blocked By:
 Blocking:          |  Operating System:  All
--------------------+---------------------------
Changes (by olly):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 Implemented in [27592d05bc6de402ada8cacbd42661e1bb3c4359].

 I've changed around `R` and `F` in the `$filters` encoding - this changed
 to a new encoding in 1.3.4, and I think it's preferable to make this
 change between consecutive release snapshots rather than having the
 encoding be "wrong" for indefinitely.

 The consequence would be that we would/wouldn't force the first page if
 sorting on a value slot was in effect, but only once for each search
 session spanning an upgrade, or if such a search URL had been bookmarked,
 the meaning of it would change.

--
Ticket URL: <https://trac.xapian.org/ticket/697#comment:10>
Xapian <//xapian.org/>
Xapian