relation "bitten_log" does not exist

[anonymous]

After migrating an SQLite installation of Trac over to Postgres (and updating the version of Bitten to rev 626), I'm receiving the following message when I attempt to do a trac_admin upgrade:

Add filename column to log table to save where log files are stored.
Traceback (most recent call last):
  File "/usr/bin/trac-admin", line 8, in <module>
    load_entry_point('Trac==0.11.4', 'console_scripts', 'trac-admin')()
  File "/usr/lib/python2.5/site-packages/Trac-0.11.4-py2.5.egg/trac/admin/console.py", line 1317, in run
    return admin.onecmd(command)
  File "/usr/lib/python2.5/site-packages/Trac-0.11.4-py2.5.egg/trac/admin/console.py", line 133, in onecmd
    rv = cmd.Cmd.onecmd(self, line) or 0
  File "/usr/lib64/python2.5/cmd.py", line 219, in onecmd
    return func(arg)
  File "/usr/lib/python2.5/site-packages/Trac-0.11.4-py2.5.egg/trac/admin/console.py", line 1154, in do_upgrade
    self.__env.upgrade(backup=do_backup)
  File "/usr/lib/python2.5/site-packages/Trac-0.11.4-py2.5.egg/trac/env.py", line 458, in upgrade
    participant.upgrade_environment(db)
  File "build/bdist.linux-x86_64/egg/bitten/main.py", line 74, in upgrade_environment
  File "build/bdist.linux-x86_64/egg/bitten/upgrades.py", line 291, in add_filename_to_logs
  File "/usr/lib/python2.5/site-packages/Trac-0.11.4-py2.5.egg/trac/db/util.py", line 51, in execute
    return self.cursor.execute(sql)
  File "/usr/lib/python2.5/site-packages/Trac-0.11.4-py2.5.egg/trac/db/util.py", line 51, in execute
    return self.cursor.execute(sql)
psycopg2.ProgrammingError: relation "bitten_log" does not exist

[dfraser]

How did you do the migration? bitten_log is part of the standard schema in both databases...

[anonymous]

I used the script found at ​http://trac-hacks.org/wiki/SqliteToPgScript

[anonymous]

If it helps at all, I'm coming from Bitten rev559 on the old database

[dfraser]

Looks like that script gets the list of tables you want to migrate from postgres ... wierd ... will try have a better look later

[anonymous]

Still experiencing the same issues. I can do an environment upgrade successfully without Bitten installed, but as soon as I add the plugin, I get the error outlined above.

[dfraser]

Have you tried upgrading trac before transfering to postgresql?

[anonymous]

That seems to have worked... Copied over old environment... Then upgraded Trac, plugins, etc... Upgraded Trac database... Migrated from SQLite to Postgres... Works perfectly... Thanks!

Something to note (which may help you in debugging this issue) is when I did the Trac DB upgrade (on the SQLite DB), I get two messages that I don't get when I try (and fail) upgrading on Postgres:

Add filename column to log table to save where log files are stored.
Done.
Migrates logs that are stored in the bitten_log_messages table into
files.
Done.

[dfraser]

OK, we've had reports of people successfully upgrading on Potsgres so I'm closing this as wontfix since it seems this only happens if you both switch from sqlite to postgres and try upgrade in one go.