Version 9 (modified by trac, 9 years ago) ( diff )

--

Trac Ticket Queries

Table of Contents

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 on 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.

After you have edited your filters, click the Update button to refresh your results.

Some shortcuts can be used to manipulate checkbox filters.

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

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.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

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

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 in by placing pipes (|) between the columns: 

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

[[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 34942)

1 2 3 4 5 6 7 8 9 10 11 →
Ticket Resolution Summary Owner Reporter
#36797 wontfix Implement fully async-capable support for django.middleware.common.CommonMiddleware Mykhailo Havelia
Description

From the Django documentation:

You will only get the benefits of a fully asynchronous request stack if you have no synchronous middleware loaded into your site.

Currently, all of Django's internal middleware uses MiddlewareMixin and relies on sync_to_async under the hood. This makes it difficult for end users to have a fully async request flow, because they would need to copy and adapt all internal logic for each middleware, and maintain it across Django releases.

Some internal middleware only performs CPU-bound operations and does not require async/AIO logic, so it could safely be used in both sync and async contexts without sync_to_async.

Options to solve this

  • Implement __acall__ without sync_to_async

Not recommended. Can lead to subtle bugs if users subclass and customize the middleware: 

class CustomCommonMiddleware(CommonMiddleware):
    def process_response(self, request, response):
        # custom logic
        return super().process_response(request, response)

In an async context, this custom logic would be ignored or behave unexpectedly.

  • Rewrite middlewares using sync_and_async_middleware decorator

Safe and straightforward. Breaking change: would break all existing custom middleware that inherits from the internal middleware.

  • Implement separate async middleware (AsyncCommonMiddleware)

Compromise solution. Safe for users: they can explicitly replace CommonMiddleware with AsyncCommonMiddleware in async setups. When MiddlewareMixin is eventually removed, we can rename AsyncCommonMiddleware -> CommonMiddleware without breaking changes.

I'm going to start by implementing an async version of CommonMiddleware as a test case for this approach. Once we validate it, the plan is to extend the same pattern to:

  • django.contrib.auth.middleware.AuthenticationMiddleware
  • django.middleware.locale.LocaleMiddleware
  • django.middleware.security.SecurityMiddleware

If you have any thoughts or concerns about this approach, especially regarding edge cases or backward compatibility, please share them.

#36792 duplicate Add support for virtual generated columns (PostgreSQL 18+) in GeneratedField Paolo Melchiorre
Description

Background

PostgreSQL 18 introduces virtual generated columns: columns declared with GENERATED ALWAYS AS ( <generation_expr> ) VIRTUAL are computed at query time and do not occupy storage. PostgreSQL 18 also makes VIRTUAL the default for generated columns while continuing to support STORED (materialized) generated columns. See the PostgreSQL 18 release notes: ​PostgreSQL 18 release notes.

Motivation

Django's GeneratedField support currently targets databases that support STORED (materialized) generated columns. With PostgreSQL 18, users should be able to declare GeneratedFields that are VIRTUAL (computed at query time) and have Django generate the correct DDL and perform correct introspection and migration autogeneration.

Goals

  • Add support in Django's PostgreSQL backend to emit the VIRTUAL keyword in CREATE TABLE and ALTER TABLE statements for generated columns when targeting PostgreSQL 18 or newer.
  • Extend PostgreSQL introspection to detect whether an existing generated column is STORED or VIRTUAL and populate migration state accordingly so autogeneration can produce correct AddField / AlterField operations.
  • Ensure migration operations handle switching between STORED and VIRTUAL where supported by the server, and emit clear errors or warnings when not supported by the connected server version.
  • Add tests and documentation; skip/guard tests on PostgreSQL servers older than 18.

Implementation notes and suggestions

  • Server gating: use the existing server_version_int checks (treat PostgreSQL 18 as the cutoff, e.g. 180000) so that DDL including VIRTUAL is only emitted on servers that support it.
  • DDL generation: update the PostgreSQL schema editor (schema creation/alter) to emit either "VIRTUAL" or "STORED" based on field metadata and server version. If the field model exposes a stored boolean, emit STORED when True and VIRTUAL when False (and server >= 18).
  • Introspection: extend postgresql introspection to read the generation expression and the storage type (stored vs virtual) from information_schema and/or pg_catalog and expose those details in the field_info consumed by the migration autogenerator.
  • Migrations: ensure AlterField and AddField include the storage attribute and that migration autogeneration treats changes in stored/virtual as schema changes. If the connected server does not support VIRTUAL, raise a clear error during migration planning/execution.
  • Tests: add backend tests that:
    • create a model with a GeneratedField stored=True (STORED) and stored=False (VIRTUAL),
    • introspect an existing table with VIRTUAL columns,
    • autogenerate migrations for switching between STORED and VIRTUAL,
    • ensure tests are skipped on PostgreSQL < 18.
  • Documentation: update GeneratedField docs to describe the stored vs virtual option and PostgreSQL version requirements (PG 18+ for VIRTUAL). Recommend keeping DB versions consistent across environments.

Examples

SQL (PG18+): 

CREATE TABLE example (
    a integer,
    b integer GENERATED ALWAYS AS (a + 1) VIRTUAL
);

Stored column: 

CREATE TABLE example (
    a integer,
    b integer GENERATED ALWAYS AS (a + 1) STORED
);

Django (draft API): 

class MyModel(models.Model):
    width = models.IntegerField()
    area = models.GeneratedField(models.F('width') * 2, stored=False)  # VIRTUAL on PG18+

Backward-compatibility and migration considerations

  • Emit VIRTUAL only when connected to PG 18+; otherwise use STORED or raise a clear error.
  • Autogenerated migrations created on PG18 that include VIRTUAL should be documented or guarded to avoid failures on older servers.
  • Recommend teams keep DB versions consistent across dev/test/prod if they plan to use VIRTUAL columns.
#36790 wontfix Add a generic error view handler Wes P.
Description

In a PR review discussion (see: ​https://github.com/django/django/pull/17960/files) which was reviewing ticket #35281 (adding a new handler for 413 errors) it was expressed that there should be a better way to allow developers to access handlers instead of creating handlers for every kind of 4xx or 5xx error: a generic method. Ticket #35281 switched from being about a 413 handler (fairly easy) to refactoring error view handlers.

I would like ticket #35281 to revert to being about handling 413 errors (which was accepted) and for this ticket to be about refactoring error view handlers to be generic. I would also recommend that we preserve backward compatibility without deprecating the existing handlers.

Documentation for error views: ​https://docs.djangoproject.com/en/6.0/ref/views/#error-views

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. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery

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