help: how mantis 0.18 upgrade to 1.0rc2?

wangxuefeng · Post by **wangxuefeng** » 13 Sep 2005, 07:17

when i upgrade my mantis 0.18 to 1.0rc2, there are errors below:
BAD
CREATE TABLE mantis_bug_file_table ( id INTEGER UNSIGNED NOT NULL AUTO_INCREMENT, bug_id INTEGER UNSIGNED NOT NULL DEFAULT 0, title VARCHAR(250) NOT NULL DEFAULT '', description VARCHAR(250) NOT NULL DEFAULT '', diskfile VARCHAR(250) NOT NULL DEFAULT '', filename VARCHAR(250) NOT NULL DEFAULT '', folder VARCHAR(250) NOT NULL DEFAULT '', filesize INTEGER NOT NULL DEFAULT 0, file_type VARCHAR(250) NOT NULL DEFAULT '', date_added DATETIME NOT NULL DEFAULT '1970-01-01 00:00:01', content LONGBLOB NOT NULL, PRIMARY KEY (id) )TYPE=MyISAM
Table 'mantis_bug_file_table' already exists

who can tell me how to solve the problem? thanks!

Guest · Post by **Guest** » 14 Sep 2005, 12:26

Important: Backup your mantis database first.

If you had no mantis_bug_file_table before the upgrade, you can drop it.
Drop table mantis_bug_file_table;

Then it will work.

Guest · Post by **Guest** » 15 Sep 2005, 09:46

thank you very much, i will try.
If the data in 'mantis_bug_file_table' has no use in new version?

wangyingying · Post by **wangyingying** » 16 Sep 2005, 01:09

I droped the 'mantis_bug_file_table',but it errors bellow:
BAD
CREATE TABLE mantis_bug_history_table ( user_id INTEGER UNSIGNED NOT NULL DEFAULT 0, bug_id INTEGER UNSIGNED NOT NULL DEFAULT 0, PRIMARY KEY (user_id, bug_id) )TYPE=MyISAM
Table 'mantis_bug_history_table' already exists
Checks Failed...

when I drop the mantis_bug_history_table ,it give me a cue:
Table 'mantis_bug_monitor_table' already exists
Checks Failed...

Guest · Post by **Guest** » 16 Sep 2005, 01:37

Anonymous wrote:Important: Backup your mantis database first.

If you had no mantis_bug_file_table before the upgrade, you can drop it.
Drop table mantis_bug_file_table;

Then it will work.

I had many data in mantis_bug_file_table, need i restore them manually?

Narcissus · Post by **Narcissus** » 16 Sep 2005, 11:05

Just restore your backup file... you did make a backup file, didn't you??

Obviously the problem is that the new database code thinks that you don't have an installation at the moment. Better than dropping tables (which is obviously a bad thing if you do have data) would be to actually work out how /why it determines that you need to create databases then go from there.

What version of OS, PHP, MySQL are you running?