wiki:TracQuery

Version 1 (modified by trac, 15 years ago) (diff)

--

Trac Ticket Queries

Table of Contents

In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page the default filter will display tickets relevant to you:

  • If logged in then all open tickets it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged and no name/email defined in the preferences then all open issues are displayed.

Current 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.

You 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.

Once you've edited your filters click the Update button to refresh your results.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page. 

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria (see Query Language).

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character: 

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Using the [[TicketQuery]] Macro

The  TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

Example: 

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

No results

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language.

A more compact representation without the ticket summaries is also available: 

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

No results

Finally, if you wish to receive only the number of defects that match the query, use the count parameter. 

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

0

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field> - you can specify multiple fields and what order they are displayed by placing pipes (|) between the columns like below: 

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 130)

Ticket Resolution Summary Owner Reporter
#143 fixed 关于jspf文件的使用问题 yuanhuoqing
#141 fixed 停电造成mongodb损坏故障 chenchongqi
#139 fixed 品牌排位接口死循环bug总结 黄育才 huangyucai

Full rows

In table format you can also have full rows by using rows=<field> like below: 

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 130)

Ticket Resolution Summary Owner Reporter
#143 fixed 关于jspf文件的使用问题 yuanhuoqing

Reported by yuanhuoqing, 12 years ago.
Description

问题：产品库wap简版页面修改计数器代码加了个公共的jspf页面，具体代码是：<jsp:include page="xx.jspf" flush="true">

<jsp:param name="counterId" value="${counterId}"/>

</jsp:include>

用jsp动态包含这个jspf文件后页面显示的内容是没有编译直接把源码包含进来了。

问题分析：

jspf并不是像jsp一样是JSP Servlet的默认的扩展名（Tomcat 5.0.28/Servlet 2.4/JSP 2.0），用jsp动态包含后jsp引擎不会把他当做jsp文件来编译，如果使用tomcat，需求在tomcat下的web.xml中加入一个

<servlet-mapping>

<servlet-name>jsp</servlet-name> <url-pattern>*.jspf</url-pattern>

</servlet-mapping>

让jspf扩展名同样成为JSP Servlet处理的文件。

如果使用resin，需要在resin中的resin.conf中<servlet-mapping url-pattern='*.jspf' servlet-name='jsp'/>

这样用jsp动态包含后jsp引擎才会把他当做jsp文件来编译。但如果用静态包含（@include）则不用做如上配置可以编译，为什么静态包含文件则可以呢，具体原因可以参见jsp的动态包含和静态包含文件的区别： http://blog.csdn.net/itautomn/article/details/1635726

注意点：不建议无端引进jspf类型文件进来，因为编辑jspf类型文件上的java代码没有jsp打点提示，不方便维护，同时引入jspf类型文件也没有什么好处反而增加了配置的复杂，当然引入jspf组件（记得有个jspf.jar）另议，因为此jspf非彼jspf。

#141 fixed 停电造成mongodb损坏故障 chenchongqi

Reported by chenchongqi, 13 years ago.
Description

由于IDC机房突然断电，恢复供电后检查应用时，发现R系统的硬缓存mongodb有异常，经检查发现集群中三台服务器有两台的数据文件已经损坏，具体表现为手工连接上去后，输入show tables显示有异常无法正常列出集合。

剩下的一台也有一定程度的损坏，具体表现为，数据更新时抛出异常： 

[09-16 21:48:22.893] 2013-09-16 21:48:22,881 [pool-1-thread-10] ERROR cn.com.pconline.core.r.MongoRClientHelper - [MongoRClientHelper] update cache:http://
m.pconline.com.cn/yp/company_price_js4.jsp?productID=364301&areaID=100&notjs=true&time=14400 error
[09-16 21:48:22.893] com.mongodb.MongoException: getFile(): bad file number value (corrupt db?): run repair
[09-16 21:48:22.893]    at com.mongodb.CommandResult.getException(CommandResult.java:82)
[09-16 21:48:22.893]    at com.mongodb.CommandResult.throwOnError(CommandResult.java:116)
[09-16 21:48:22.893]    at com.mongodb.DBTCPConnector._checkWriteError(DBTCPConnector.java:131)
[09-16 21:48:22.893]    at com.mongodb.DBTCPConnector.say(DBTCPConnector.java:153)
[09-16 21:48:22.893]    at com.mongodb.DBTCPConnector.say(DBTCPConnector.java:137)
[09-16 21:48:22.893]    at com.mongodb.DBApiLayer$MyCollection.update(DBApiLayer.java:336)
[09-16 21:48:22.893]    at com.mongodb.DBCollection.save(DBCollection.java:630)
[09-16 21:48:22.893]    at com.mongodb.DBCollection.save(DBCollection.java:597)
[09-16 21:48:22.893]    at cn.com.pconline.core.r.RRepository.save(RRepository.java:52)
[09-16 21:48:22.893]    at cn.com.pconline.core.r.MongoRClientHelper.update(MongoRClientHelper.java:60)
[09-16 21:48:22.893]    at cn.pconline.r.client.RClient.doGet(RClient.java:448)
[09-16 21:48:22.893]    at cn.pconline.r.client.RClient$3.call(RClient.java:353)
[09-16 21:48:22.893]    at cn.pconline.r.client.RClient$3.call(RClient.java:350)
[09-16 21:48:22.893]    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[09-16 21:48:22.893]    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[09-16 21:48:22.893]    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
[09-16 21:48:22.893]    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
[09-16 21:48:22.893]    at java.lang.Thread.run(Thread.java:619)

因为硬缓存使用的是price_front_cache库，于是对这个库做了修复操作，该库有55G大，修复耗时比较长。但是修复操作后应用还是报同样的异常，经查询资料后发现还需要修复admin、local库，于是一一修复，该异常不再出现。

修复后的这台数据库，直接通过虚拟机克隆出另外两台，组建了新的集群并用回原ip提供服务，目前状况正常。

Tips: 直接克隆虚拟机比拷贝数据文件过去重建速度要快，因为拷贝文件还涉及到一些底层数据校验之类的。

#139 fixed 品牌排位接口死循环bug总结 黄育才 huangyucai

Reported by huangyucai, 13 years ago.
Description

一、问题展示 1)cms报障，接口不能出数据，请求响应慢 2)检查服务器负载高，超过6.0，但是其他能正常访问 3)用threads.jsp检查发现

brand_type_top_json.jsp的线程一直在运行

初步判断可能：

1、接口被刷 2、程序存在死循环

应急解决：

试着重启一台服务器，检查负载，发现不会升高

二、问题代码 1、代码段 

    for (int i =0, size = brandList.size(); i < size; i ++) {
    	brandId=0;
    	if(fixMap!=null&&fixMap.get(index+1)!=null){//如果存在固定排位
    		brandId=Integer.parseInt(fixMap.get(index+1).toString());//获取品牌的id
    	}
    	
    	if(brandId==0){//没有固定排位则从列表获取品牌的id
    		record = (Record)brandList.get(i);
    	    brandId = record.getValue("ID").asInt();
    	}else{//否则回退一次列表
    		i--;
    	}
    	
    	//去重处理
    	if(brandSet.contains(brandId)) continue;//如果已经有品牌id就跳过不添加
    	brandSet.add(brandId);
        
        //...省略封装json的代码

		index++;//条数自增
		if(index>=max) break;//达到数量就跳出
  }

2、bug产生过程

死循环Bug分析：

当brandList.size()=10,

brandList.get(2).getValue("ID").asInt()=39127 fixMap<10,39127>

循环当i=9

执行 brandId=Integer.parseInt(fixMap.get(index+1).toString());

执行 i--;

执行 if(brandSet.contains(brandId)) continue;如果已经有品牌id就跳过

不添加

此时i=8 执行循环i++

i=9

再执行循环，构成死循环

三、修改代码

加多两次循环,让代码结构和逻辑明朗化 

	for(int i=0;i<brandList.size();i++){//先存入到brandIdList
		record = (Record)brandList.get(i);
		brandIdList.add(record.getValue("ID").asString());
	}
	if(fixMap!=null){//如果存在固定排位
		int size=brandIdList.size();//长度
		for(int i=0;i<size;i++){//迭代
			Object fixed=fixMap.get(i+1);
			if(fixed!=null){//如果指定当前位置中有固定
				if(brandIdList.contains(fixed.toString())){//如果已经存在，则先删除
					brandIdList.remove(fixed.toString());
				}
				brandIdList.add(i,fixed.toString());//添加到固定位置
			}
		}
	}
	for(int i=0;i<max&&i<brandIdList.size();i++){//迭代组装json
        }

四、总结：

1）逻辑较为复杂接口，在实现的时候要一步步来，代码要详细，条理清晰，这样可读性好，而且不容易出错 2）上线前测试要充分，不急于求成

Query Language

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 (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

The 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.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide