Number syntax has two different forms, depending on whether it's part of a field search or a post search.
Integer / Float / Datetime / Interval fields
When searching with numbers, the following variation in search parameters may be used.
These take the text field in its entirety when making the comparison as selected by the qualifier. The following qualifiers are available.
- (No qualifier) - Basic comparison.
*_not- Basic comparison (negated).
*_eq- Direct comparison.
*_not_eq- Direct inequality comparison.
*_gt- Greater-than comparison.
*_gteq- Greater-than or equal comparison.
*_lt- Less-than comparison.
*_lteq- Less-than or equal comparison.
Searches for records where the ID is 100.
- 100,200,300 (the values 100, 200 and 300)
Less than or equal to
- <100 (less than only)
- <=100 (less than or equal to)
Greater than or equal to
- >100 (greater than only)
- >=100 (greater than or equal to)
- 100..200 (all numbers between 100 and 200, inclusive)
- 100...200 (all numbers between 100 and 200, excludes 200)
- ..100 (equivalent to <=100)
- 100.. (equivalent to >=100)
Note: intervals only work from low to high, i.e. 100..200 will work while 200..100 won't.
In post searches, the syntax goes like this:
Values can be passed in using the basic syntax.
Metatags where basic syntax can be used
copytags[/i] * [code]pixiv
Metatags where basic syntax cannot be used
pool[/i] h5. Units With certain metatags, units are used. The basic syntax works the same with units. Syntax: [code][metatag]:[number][unit]
These units are used together with the age metatag.
- seconds (s)
- minutes (mi)
- hours (h)
- days (d)
- weeks (w)
- months (mo)
- years (y)
The shorthand version is in parenthesis. You can use any number of characters between the shorthand version and full version. For example, "se" or "sec" work in place of s or seconds.
Note: not specifying the time unit is no longer supported and will return no results. "m" will also return no results as it is ambiguous between minutes and months.
Note: singular and plural forms of units can be used interchangeably.
These units are used together with the filesize metatag.
- b (bytes)
- kb (kilobytes)
- m (megabytes)
Only the shorthand versions will work, i.e. bytes, kilobytes and megabytes are not part of the syntax.
Note: if no unit is specified it defaults to bytes.
Note: for anyone curious, 1m = 1024kb and 1kb = 1024b.
For the metatag ratio, fractions are commonly used but you may use decimal notation also.
The aspect ratio denotes the relationship between the width and height of an image. For example, a 1:1 ratio means the width and height are equal whereas a 4:3 ratio means the width is one third longer (4/3) than the height. Useful aspect ratio tool: http://andrew.hedges.name/experiments/aspect_ratio/
Note: colons are supported in place of slashes; e.g., ratio:16:9.Note: using ratios won't always result in pixel perfect results as the ratios are rounded to two decimal points, i.e. a search for ratio:16/9 may result in a picture with the dimensions 1920x1078 instead of 1920x1080.
Why should you use ratios?
Ratios can be used to assist in finding wallpapers. For example, if you have a 1920x1080 monitor, you can use ratio:16/9 width:>=1920 to find wallpapers for it.
If you want to avoid calculating ratios altogether, then you can use dimensions directly.
You can use basic syntax with ratios; though, take note if you use fractions.
At this point it's regular numbers and normal basic syntax will work as expected.