www.delorie.com/gnu/docs/gnats/query-pr.man.html   search  
Buy GNU books!




Non-network-mode options:

Network-mode-only options:

Deprecated Options





The not-equal operator. Produces the opposite result of the == operator.
The left-hand side must have a value less than or greater than the right-hand side. Comparisons are done depending on the type of data being queried; in particular, integer fields and dates use a numeric comparison, and enumerated fields are ordered depending on the numeric equivalent of their enumerated values.

booleanop is either | [or], or & [and]. The query expression

is identical to the second query example with --or given earlier; it selects all PRs with a Category field of baz or a Responsible field of blee.

The not operator ! may be used to negate a test:

searches for PRs where the category is not equal to the regular expression foo.

Parenthesis may be used to force a particular interpretation of the expression:

skips PRs where the Category field is equal to foo and the Submitter-Id field is equal to blaz. Parenthesis may be nested to any arbitrary depth.

Fieldnames can be specified in several ways. The simplest and most obvious is just a name:

checks the value of the category field for the value "foo".

A fieldname qualifier may be prepended to the name of the field; a colon is used to separate the qualifier from the name. To refer directly to a builtin field name:

In this case, Number is interpreted as the builtin name of the field to check. (This is useful if the fields have been renamed. For more discussion of builtin field names, see dbconfig(5).)

To scan all fields of a particular type, the fieldtype qualifier may be used:

searches all text fields for the regular expression bar.

Note that it is not necessary that the right-hand side of the expression be a literal string. To query all PRs where the PR has been modified since it was closed, the expression

will work; for each PR, it compares the value of its Last-Modified field against its Closed-Date field, and returns those PRs where the values differ. However, this query will also return all PRs with empty Last-Modified or Closed-Date fields. To further narrow the search:

In general, comparing fields of two different types (an integer field against a date field, for example) will probably not do what you want.

Also, a field specifier may be followed by the name of a subfield in braces:

or even

Subfields are further discussed in dbconfig(5).





  webmaster   donations   bookstore     delorie software   privacy  
  Copyright 2003   by The Free Software Foundation     Updated Jun 2003