Modify ↓
Opened 17 years ago
Closed 16 years ago
#4862 closed defect (fixed)
Running trac-admin upgrade fails after installing this plugin with PostgreSQL
| Reported by: | Owned by: | Richard Liao | |
|---|---|---|---|
| Priority: | normal | Component: | TracTicketTemplatePlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.11 |
Description
Using Trac 0.11.3, with Postgresql database. Installed the TracTicketTemplate plugin, and Trac told me to run trac-admin upgrade. Running "trac-admin upgrade --no-backup" fails with this error:
Traceback (most recent call last):
File "/usr/bin/trac-admin", line 7, in ?
sys.exit(
File "/usr/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/admin/console.py", line 1317, in run
return admin.onecmd(command)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/admin/console.py", line 133, in onecmd
rv = cmd.Cmd.onecmd(self, line) or 0
File "/usr/lib/python2.4/cmd.py", line 219, in onecmd
return func(arg)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/admin/console.py", line 1154, in do_upgrade
self.__env.upgrade(backup=do_backup)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/env.py", line 458, in upgrade
participant.upgrade_environment(db)
File "build/bdist.linux-x86_64/egg/tickettemplate/ttadmin.py", line 93, in upgrade_environment
File "build/bdist.linux-x86_64/egg/tickettemplate/ttadmin.py", line 69, in environment_created
File "/usr/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/db/util.py", line 51, in execute
return self.cursor.execute(sql)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/db/util.py", line 51, in execute
return self.cursor.execute(sql)
psycopg2.ProgrammingError: column "tt_name,modi_time" does not exist}}}
Attachments (0)
Change History (2)
comment:1 Changed 16 years ago by
| Summary: | trac-admin upgrade fails after installing this plugin → Running trac-admin upgrade fails after installing this plugin with PostgreSQL |
|---|
Note: See
TracTickets for help on using
tickets.



Probably specific to PostgreSQL because of what I noted in ticket:4931:comment:3.