I tried to understand why there's no "kind" column, although it's a first install.
In fact, the db17 is working well, but db18 fails !! But if I do an upgrade again, the db17 fails because the "system" table claim the db is always in version 16... So here is the "real" message : # /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.pyc matches /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.py import trac.upgrades.db17 # precompiled from /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.pyc # /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db18.pyc matches /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db18.py import trac.upgrades.db18 # precompiled from /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db18.pyc Command failed: columns sid, authenticated, name are not unique On 9/13/06, Christian Boos <[EMAIL PROTECTED]> wrote: > > nomorsad wrote: > > Hi, > > > > I try to upgrade my Trac from 0.9.4 to 0.10b1 but the "trac-admin > > uprgade" fails. > > > > ... > > Command failed: no such column: kind > > > > > > My db is in version 16: > > sqlite> select * from system; > > database_version|16 > > [...] > > > > > What do you get with: > sqlite> .schema node_change > > Anyway, a quick workaround would be to comment out the `cursor.execute` > statements > (but the one dropping the 'node_change' table, if the table still > exists), redo an 'upgrade', > then a 'resync'. > > It would still be interesting to understand why you had a 'node_change' > table without a 'kind' column... > > -- Christian > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---
