On 03.08.2013 04:06, ilewismsl wrote:
On Friday, August 2, 2013 4:23:12 AM UTC-8, Peter Suter wrote:
I found #9736, #10152 and #10866.
And #8329.
http://trac.edgewall.org/ticket/8329
Thank you for replying, Peter. most of these tickets seem to be
related to the custom query module, rather than the TicketQuery()
macro, but #10152 does seem to indicate something similar to what I see.
The TickeQuery() macro and the QueryModule share a lot of code and
limitations.
I still think this looks like a defect, not an "as designed", though I
also am still not sure whether to report a defect or not.
It looks like an unfortunate limitation to me. A design error if you
will. But not a defect in the sense that one could find a spot in the
code where it says "or" but it should say "and" and fixing the defect
would simply change that.
Removing this limitation would likely require a (major or minor)
redesign that carefully considers all the existing behavior as well as a
the list of other known limitations and desired improvements.
If you think four tickets I listed don't include your case I would
recommend adding a ticket so it may be considered when such a redesign
ever happens.
Peter
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.
