Modify ↓
Opened 18 years ago
Closed 18 years ago
#812 closed defect (duplicate)
TracEnv won't upgrade
Reported by: | anonymous | Owned by: | Radek Bartoň |
---|---|---|---|
Priority: | normal | Component: | DiscussionPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
After installing from source and modifying the trac.ini configuration to include Discussion. I have to upgrade the environment, but it doesn't work:
#!/bin/bash devspot:~/discussionplugin/0.10# trac-admin /tracenvironment/ upgrade Database is up to date, no upgrade necessary.
So I get errors about column names when I try Discussion :
Traceback (most recent call last): File "/var/lib/python-support/python2.3/trac/web/main.py", line 356, in dispatch_request dispatcher.dispatch(req) File "/var/lib/python-support/python2.3/trac/web/main.py", line 224, in dispatch resp = chosen_handler.process_request(req) File "build/bdist.linux-i686/egg/tracdiscussion/core.py", line 70, in process_request File "build/bdist.linux-i686/egg/tracdiscussion/api.py", line 31, in render_discussion File "build/bdist.linux-i686/egg/tracdiscussion/api.py", line 352, in _do_action File "build/bdist.linux-i686/egg/tracdiscussion/api.py", line 785, in get_groups File "/var/lib/python-support/python2.3/trac/db/util.py", line 48, in execute return self.cursor.execute(sql) File "/usr/lib/python2.3/site-packages/sqlite/main.py", line 244, in execute self.rs = self.con.db.execute(SQL) DatabaseError: no such column: g.id
Attachments (0)
Note: See
TracTickets for help on using
tickets.
This is the duplicate of ticket #790, but thank you for reporting. Changes I made didn't help to solve this problem on some systems. Could you report info about your sqlite and pysqlite version to ticket #790. Perhaps some versions of sqlite has problem with this SQL statement:
but I don't know yet which versions and why.