Re: [Bug?] Filtering on property=-1 and ordering by the same property at the same time
Nagy Gabor <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <20210512193731.192e434d@Dell> |
> On Tue, May 11, 2021 at 11:30:10PM +0200, Nagy Gabor wrote: > > Dear Roundup users, > > > > I found a strange behaviour in my roundup tracker. I am not sure if > > this is a bug (it was mentioned in this ML, that filtering has some > > tricky options with negative numbers). If it is a bug, I will report > > this in the bug tracker too. > > > > Symptom: > > > > http://localhost:8080/tracker/issue?@filter=status&status=-1,2 > > > > lists all issues with status -1 (unset) or 2 (deferred). > > > > However, in the list of > > > > http://localhost:8080/tracker/issue?@filter=status&status=-1,2&@sort=status > > > > issues with status -1 are missing. > > Can you retry without sorting? > As far as I know, for Link properties (like status) you cannot combine > -1 with other IDs, so you can either search for -1 alone or for > several IDs but not the combination. Should not make a difference if > you're sorting on the same property or not. > > Note that the same thing should (since some patches over the weekend > :-) work reliably for multilink properties. > > And, yes, it would be desirable to have the same mechanisms for Link > and Multilink props ... > > Ralf Dear Ralf, Thanks, but it seems that "filter=-1,2" etc. works as expected without sorting, e.g. in my first example. It looks also OK if you sort by a property different from status (the property that contains a -1 filter), e.g. "filter=status&status=-1,2&@sort=id" Do you say that a filter like status=-1,2 has unpredictable result? Which patch do you refer to? My reply to your other email: OK, I will not sort anything by a multilink property. :) Regards, Gábor _______________________________________________ Roundup-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/roundup-users