Version 6 (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 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.

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 using 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:

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 34831)

1 2 3 4 5 6 7 8 9 10 11 →
Ticket Resolution Summary Owner Reporter
#36687 needsinfo Unexpected IntegrityError and unavailability during Django Oracle upgrades involving AutoField/BigAutoField and pre-Django 2.0 legacy triggers behavior Fabio Caritas Barrionuevo da Luz
Description

I recently migrated a legacy project to Django 5.2 + Python 3.12 + Oracle 19c and encountered some unexpected issues.

The project started with Python 2.7 and Django 1.11 or earlier + Oracle 11 and was later migrated by someone to Django 3.0 + Oracle 12+.

Context

Until Django 1.11, the Django Oracle backend created a trigger + sequence for each AutoField and BigAutoField used in the project. See ​https://github.com/django/django/blob/stable/1.11.x/django/db/backends/oracle/operations.py#L57-L78.

Django 2.0 introduced support for identity columns in AutoField and BigAutoField on Oracle (see ​https://github.com/django/django/commit/924a89e135fe54bc7622aa6f03405211e75c06e9), but only for new tables/models. This means that a trigger + sequence was no longer necessary because identity columns have an implicit sequence created and managed automatically by Oracle. Note that support for identity columns was added in Oracle 12+.

If the project started with versions prior to Django 2.0 (Django 1.11 or lower) + Oracle 11 or lower and already has a created and populated database, then existing tables/models will have been created with a trigger + sequence for AutoField/BigAutoField.

After upgrading the codebase + database to run with Django 2.0+ and Oracle 12+, tables/models created after the upgrade will use identity columns, but the old models will continue to use the trigger + sequence, remaining fully functional and untouched.

In the future Django 6.0, the BigAutoField will be the default field for primary keys.

The consequence of this is that in some situations, this results in the creation of a new migration that will, at the database level (Oracle), change the primary key column type from NUMBER(11) or NUMBER(11) GENERATED BY DEFAULT ON NULL AS IDENTITY to NUMBER(19) GENERATED BY DEFAULT ON NULL AS IDENTITY.

This does not cause problems for tables/models created after the project is already using Django 2.0+ and Oracle 12+.

However, it can result in unique constraints errors, as there will now be an identity column for the primary key with a sequence number that may already exist in the primary key column of the table, plus a trigger + sequence competing to generate the new value for the primary key, randomly generating the error: 

django.db.utils.IntegrityError: ORA-00001: unique constraint (<DB_USER>.SYS_C<ID>) violated
Help: https://docs.oracle.com/error-help/db/ora-00001/

The point here is that, although the migration plan for BigAutoField to be the default primary key type has been underway for some time, I could not find any warning in the documentation about the existence of triggers in Django 1.11 or lower, and I did not see or do not recall seeing any Django warning that there would be a trigger and that it could interfere with identity on Oracle 12+ and Django 2.0+.

Tools like django-upgrade and django-codemod also did not catch this.

Suggestions

I think it would be prudent before the release of Django 6.0 to:

  1. Document the behavior in the release notes for Django 2.0.
  2. Document the behavior in the release notes for Django 6.0.
  3. Perhaps create a migration guide to how to safe migrate from trigger + sequence to identity on Oracle and link it in the documentation for AutoField and BigAutoField in all versions.
  4. In the documentation for AutoField and BigAutoField in Django 2.0 and all subsequent versions, inform about the old behavior regarding the trigger.
  5. Perhaps improve the way migrations from AutoField to BigAutoField are done and include the detection of the existence of the trigger + sequence and inform how to resolve it.
  6. Perhaps introduce some new functionality to be executed when running manage.py makemigrations or manage.py check and thus issue a warning.

Note that Django's native application tables, such as auth, admin, contenty_type, etc., do not generate any migrations or warnings, even with DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField' set in the settings. They continue to use the trigger + sequence combination if the project born from a very old version of Django (Django 1.11 or lower + Oracle 11 or lower )

This may not be worth maintaining for the same reason that BigAutoField is now the default primary key type on Django 6.0

A migration path/guide for these should probably be created for native django app.

#36685 duplicate `max_size` and `min_size` validation for `FileField` amirreza amirreza
Description

hi as disccussed in ​forum, i think a max_size and min_size validation could be a good addition to django or at least max_size

should mention i can do this one myself

i'm fine by doing it as a paarameter in FormField, or as a validator function so if you have a preference, please do tell

should mention anything discussed here also applies to ImageField and anything else inheriting from FormField

#36684 duplicate `max_size` and `min_size` validation for `FileField` amirreza amirreza
Description

hi as disccussed in ​forum, i think a max_size and min_size validation could be a good addition to django or at least max_size

should mention i can do this one myself

i'm fine by doing it as a paarameter in FormField, or as a validator function so if you have a preference, please do tell

should mention anything discussed here also applies to ImageField and anything else inheriting from FormField

1 2 3 4 5 6 7 8 9 10 11 →

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 litteral & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches the 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

Note: See TracWiki for help on using the wiki.
Back to Top