Normally when I set multiple conditions on TicketQuery() the macro uses AND to combine the conditions (unless I use the ,or, syntax). For example, if I enter the following on http://trac.edgewall.org/wiki/QueryTest and Preview [[TicketQuery(component~=system,status!=closed,group=component,priority=high, format=table)]] As expected, I get all the tickets where the component contains the word "system" AND status not closed AND priority high. Now, if I modify this to add a second condition on the component that it starts with "r" I would expect to further restrict the tickets listed and only get back "report system" [[TicketQuery(component~=system,component^=r,status!=closed,group=component,priority=high, format=table)]] However, instead, the query seems to switch to using some kind of OR operator and I get back lots of tickets where the component does not include the word "system". This looks like a bug to me, but I find no ticket for it. Can someone tell me whether this is a defect? If it is not a defect, then why is the query language doing what it is. It makes no sense to me. Ian Lewis www.mstarlabs.com Using Trac 1.0.0, Python 2.6, Apache, on Windows 7.
-- 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.
