Bienvenue sur PostGIS.fr

Bienvenue sur PostGIS.fr , le site de la communauté des utilisateurs francophones de PostGIS.

PostGIS ajoute le support d'objets géographique à la base de données PostgreSQL. En effet, PostGIS "spatialise" le serverur PostgreSQL, ce qui permet de l'utiliser comme une base de données SIG.

Maintenu à jour, en fonction de nos disponibilités et des diverses sorties des outils que nous testons, nous vous proposons l'ensemble de nos travaux publiés en langue française.

Changes between Version 1 and Version 2 of TracQuery


Ignore:
Timestamp:
21/09/2011 11:27:42 (13 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracQuery

    v1 v2  
    1313 * If not logged and no name/email defined in the preferences then all open issues are displayed. 
    1414 
    15 Current filters can be removed by clicking the button to the right with the minus sign on the label.  New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right).  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria. 
     15Current filters can be removed by clicking the button to the left with the minus sign on the label.  New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right).  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria. 
    1616 
    1717You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket. 
    … …  
    7575  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 
    7676 
    77 Finally if you wish to receive only the number of defects that match the query using the ``count`` parameter. 
     77Finally, if you wish to receive only the number of defects that match the query, use the ``count`` parameter. 
    7878 
    7979{{{ 
    … …  
    107107=== Query Language === 
    108108 
    109 `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a litteral `&` or `|` in a value, escape the character with a backslash (`\`). 
     109`query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a literal `&` or `|` in a value, escape the character with a backslash (`\`). 
    110110 
    111111The available operators are: 
    112 || '''`=`''' || the field content exactly matches the one of the values || 
     112|| '''`=`''' || the field content exactly matches one of the values || 
    113113|| '''`~=`''' || the field content contains one or more of the values || 
    114114|| '''`^=`''' || the field content starts with one of the values || 
    … …  
    121121|| '''`!$=`''' || the field content does not end with any of the values || 
    122122 
    123 The date fields `created` and `modified` can be constrained by using the `=` operator and specifying a value containing two dates separated by a semicolon (`;`). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string.  
    124 || '''`created=2007-01-01;2008-01-01`''' || query tickets created in 2007 || 
    125 || '''`created=lastmonth;thismonth`''' || query tickets created during the previous month || 
    126 || '''`modified=1weekago;`''' || query tickets that have been modified in the last week || 
    127 || '''`modified=;30daysago`''' || query tickets that have been inactive for the last 30 days || 
     123The date fields `created` and `modified` can be constrained by using the `=` operator and specifying a value containing two dates separated by two dots (`..`). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string.  
     124|| '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 || 
     125|| '''`created=lastmonth..thismonth`''' || query tickets created during the previous month || 
     126|| '''`modified=1weekago..`''' || query tickets that have been modified in the last week || 
     127|| '''`modified=..30daysago`''' || query tickets that have been inactive for the last 30 days || 
    128128 
    129129----