Opened 2 years ago
defect #126 (new)
'OperationalError' when trying to modify (rename) a ticket relative size
| Test Complete Size: | undefined | Test Complete Date: | |
|---|---|---|---|
| Documentation Complete Size: | undefined | Documentation Complete Date: | |
| Acceptance Complete Size: | undefined | Acceptance Complete Date: | |
| Reported by: | riccardocontri | Owned by: | ja11sop |
| Milestone: | Undecided | Component: | relative sizing |
| Version: | Keywords: | ||
| Cc: | Blocked By: | ||
| Patch SVN Revision: | Patch Trac Version: | not_applicable | |
| Blocking: | |||
| In Iterations: | None |
Description
If I try to rename a ticket relative size (e.g. from 'undefined' to 'not set') I get an internal error.
Maybe renaming should not be allowed at all?
How to Reproduce
I just installed agile-trac plugin on a small demo project with few existing tickets.
While doing a POST operation on /admin/ticket/relative_size/undefined, Trac issued an internal error.
OperationalError: no such column: relative_size
Request parameters:
{'__FORM_TOKEN': u'9b7ef488192e990235431ef4',
'cat_id': u'ticket',
'name': u'not set',
'panel_id': u'relative_size',
'path_info': u'undefined',
'save': u'Save'}
User Agent was: Mozilla/5.0 (Windows; U; Windows NT 5.0; it; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7
System Information
| Trac | 0.11.5 |
| Python | 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)] |
| setuptools | 0.6c11 |
| SQLite | 3.6.11 |
| pysqlite | 2.5.5 |
| Genshi | 0.5.1 |
| mod_python | 3.3.1 |
| Subversion | 1.6.6 (r40053) |
| jQuery: | 1.2.6 |
Python Traceback
Traceback (most recent call last):
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\web\main.py", line 444, in _dispatch_request
dispatcher.dispatch(req)
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\web\main.py", line 205, in dispatch
resp = chosen_handler.process_request(req)
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\admin\web_ui.py", line 114, in process_request
path_info)
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\ticket\admin.py", line 45, in render_admin_panel
return self._render_admin_panel(req, cat, page, version)
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\ticket\admin.py", line 501, in _render_admin_panel
enum.update()
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\ticket\model.py", line 610, in update
(self.name, self._old_name))
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\db\util.py", line 59, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\db\sqlite_backend.py", line 58, in execute
args or [])
File "C:\Programmi\BitNami Trac Stack\trac\Lib\site-packages\Trac-0.11.5-py2.5.egg\trac\db\sqlite_backend.py", line 50, in _rollback_on_error
return function(self, *args, **kwargs)
OperationalError: no such column: relative_size
Note: See
TracTickets for help on using
tickets.
