#4597 closed defect (fixed)
search does not find id:0
Reported by: | CharlesNepote | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | search id 0 | Cc: | charles@…, skyper |
Description
Finding all modifications during a month for a given zone is very interesting.
Search for "timestamp:2010-02" was working fine but no longer works in version 3033.
Attachments (0)
Change History (10)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Replying to jttt:
You can try timestamp:"2010-02" (not tested)
Yes it works!
But you have to know it...
Either it must be documented.
Either "timestamp:2010-02" should be accepted.
I prefer the second solution.
comment:4 by , 15 years ago
Priority: | normal → major |
---|---|
Summary: | Search for timestamp:2010-02 no longer works → Search broken and search documentation outdated |
I can not find id:0.
nor can I find "FIXME": through search.
I tried all possibilities, but I get no result.
comment:6 by , 15 years ago
works for me (3044): Type FIXME
or FIXME=*
Bug: The latter is case sensitive although the option is unticked.
(I can confirm id:0 is broken.)
Replying to Ldp (Ticket #4621):
Fine, but what does the number mean to the search compiler, in this specific case? Is this parsing just a byproduct of the generic parsing for the other search options that have numberic modifiers, like nodes: and timestamp: ?
I think it's a defect and should be fixed.
comment:7 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:8 by , 15 years ago
Keywords: | id 0 added |
---|---|
Priority: | major → minor |
Resolution: | fixed |
Status: | closed → reopened |
Summary: | Search broken and search documentation outdated → search does not find id:0 |
comment:9 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
You can try timestamp:"2010-02" (not tested)