Modify ↓

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#11894 closed defect (fixed)

Search: ">" unexpected behavior when values are not numbers

Reported by: RicoZ Owned by: team
Priority: normal Milestone: 15.10
Component: Core Version:
Keywords: Cc:

Description

Recently was searching for wind power generators height>180. The results included many hits with height="fixme" and similar.

Maybe there need to be separate comparison operators for string and numeric comparisons though I have no idea why I would use string <,> in josm search.

Attachments (0)

Change History (3)

comment:1 by RicoZ, 9 years ago

Thinking more about it, a comparison operator taking an explicit unit might be a good thing.

comment:2 by simon04, 9 years ago

Resolution: → fixed
Status: new → closed

In 8838/josm:

fix #11894 - Search: ">" unexpected behavior when values are not numbers

key<X and key>X behave as follows:

  • missing tag for key: no match
  • if value for key or X is in ISO8601 format, perform string comparison
  • if X is a numeric value, perform numeric comparison
  • otherwise perform natural string comparison using AlphanumComparator

comment:3 by simon04, 9 years ago

Milestone: → 15.10

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.