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

[Xapian]

#697: Omega SORTREVERSE semantics confusing
--------------------+-----------------------------
 Reporter:  olly    |             Owner:  olly
     Type:  defect  |            Status:  assigned
 Priority:  normal  |         Milestone:  1.3.4
Component:  Omega   |           Version:  1.3.3
 Severity:  normal  |        Resolution:
 Keywords:          |        Blocked By:
 Blocking:          |  Operating System:  All
--------------------+-----------------------------

Comment (by james):

 #311 was seven years ago, so I don't think it's impossible to rethink
 things if we decide it's sensible. However the argument for consistency
 with C++ may be the right call. My thought was for people coming from
 outside the ecosystem, say web developers who have experience with either
 SQL (`ORDER BY … DESC|ASC`) or ORMs (some of which do things like
 `.order_by('-field_name')` to do reverse sorting). I don't actually know
 what the audience for Omega is these days, however (since a lot of web
 frameworks have an indirect way of integrating Xapian, web developers from
 those backgrounds are probably less likely to use Omega at all).

 I like the decoupling idea, but agree that it isn't right for before 1.4.
 Whether it's worth doing depends I think a little on who is using Omega
 and what their background is.

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