Opened 16 years ago
Closed 16 years ago
#7760 closed defect (invalid)
Custom query module throws error
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.11-stable |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I'm logged in as user with TRAC_ADMIN permission. When I go to "View Tickets ⇒ Custom Query" I get:
2008-10-28 08:23:32,873 Trac[main] ERROR: no such column: t.statis Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/web/main.py", line 432, in _dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/web/main.py", line 204, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/ticket/query.py", line 823, in process_request return self.display_html(req, query) File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/ticket/query.py", line 876, in display_html tickets = query.execute(req, db) File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/ticket/query.py", line 261, in execute self.num_items = self._count(sql, args, db) File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/ticket/query.py", line 246, in _count cursor.execute(count_sql, args); File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/db/util.py", line 50, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/db/sqlite_backend.py", line 58, in execute args or []) File "/usr/lib/python2.5/site-packages/Trac-0.11stable_r7613-py2.5.egg/trac/db/sqlite_backend.py", line 50, in _rollback_on_error return function(self, *args, **kwargs) OperationalError: no such column: t.statis
I verified that this is not caused by any of the plugins I have installed, by disabling all of them (with the only exception being the TracAccountManager plugin).
Version information as per the web-version of the traceback:
Trac: 0.11stable-r7613 Python: 2.5.2 (r252:60911, Sep 29 2008, 21:31:01) [GCC 4.3.2] setuptools: 0.6c8 SQLite: 3.5.9 pysqlite: 2.4.1 Genshi: 0.5.1 Pygments: 0.10 Subversion: 1.5.1 (r32289) jQuery: 1.2.6
Trac is served by Apache 2.2 with mod_wsgi.
Not sure if the following matters at all, but anyway:
The environment was originally created with Trac 0.10.4. I have migrated it to a different server which uses Trac 0.11.1. Today I have installed a snapshot of 0.11-stable branch (r7613). Unfortunately I did not check the custom query functionality before installing the snapshot today - it might well be that the issue also existed before.
Attachments (0)
Change History (6)
follow-up: 3 comment:1 by , 16 years ago
follow-up: 4 comment:2 by , 16 years ago
Could it be a custom field mistaken for a standard field?
Can you post:
- your
[ticket-custom]
section from your trac.ini? - the query url that you used for triggering the error?
comment:3 by , 16 years ago
Replying to cboos:
Any idea where this "statis" comes from?
Nope, unfortunately not.
Could you grep the installed sources to locate it (it's not in the repo).
Did that, and couldn't find statis anywhere. Not in any of the sources of the various Trac versions I've been using with this environment, nor in the sources of any of the plugins that I've been or still am using.
follow-up: 5 comment:4 by , 16 years ago
Replying to cboos:
Can you post:
- your
[ticket-custom]
section from your trac.ini?
There is no such section in the trac.ini for the environment in question.
- the query url that you used for triggering the error?
follow-up: 6 comment:5 by , 16 years ago
Replying to mrenzmann@…:
Replying to cboos:
Can you post:
- your
[ticket-custom]
section from your trac.ini?There is no such section in the trac.ini for the environment in question.
Don't forget to look into the inheritance chain (i.e. look in your [inherit] file =...
ini file, and if that one has an [inherit]
section, repeat).
- the query url that you used for triggering the error?
The default query seems misconfigured at the moment, but when creating a valid one it works. So again, what was the exact URL which triggered the problem?
comment:6 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Replying to cboos:
Don't forget to look into the inheritance chain (i.e. look in your
[inherit] file =...
ini file, and if that one has an[inherit]
section, repeat).
The inherit section looks like:
[inherit] plugins_dir = templates_dir =
No other entries.
The default query seems misconfigured at the moment,
Doh! Indeed, you're right:
[query] default_anonymous_query = status!=closed&&cc~=$USER default_query = statis!=closed&owner=$USER items_per_page = 100
default_query is where statis turns up. Obviously that's been a layer-8-issue. Sorry for the noise and the trouble I've caused. :-(
Any idea where this "statis" comes from?
Could you grep the installed sources to locate it (it's not in the repo).