Opened 12 years ago
Last modified 11 years ago
#10803 closed defect
trac 1.0beta from github does not upgrade cache table — at Version 1
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | highest | Milestone: | |
| Component: | database backend | Version: | 1.0dev |
| Severity: | blocker | Keywords: | |
| Cc: | leho@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
I found that while upgrading my existing trac instances from trac 0.12 to 1.0beta1 the upgrade is flawed in that db27.py will not be executed.
I have here trac instances using a database_version 27. On upgrade, trac will create a copy of the database file (sqlite that is) having a version identifier of 27.
It will then skip db27 and continue with db29.
In order to overcome this problem, one needs to
sqlite3 db/trac.db update system set value=26 where name = 'database_version';
and run trac <env> upgrade again…
Somebody must have "fucked up" the database migration path, as the last upgrade that I did using 0.12/0.13 already increased the database version to 27 and it did not introduce a third column to the cache table.
TIA for fixing this.
