tkusukawa / kusu

Automatically exported from code.google.com/p/kusu
0 stars 0 forks source link

Erro installing redmine_work_time - Table user_issue_months doesn't exist #57

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
When i try to install redmine_work_time-0.1.2 on Redmine 1.2.1.stable, i get 
the following error.

Migrating redmine_work_time...
==  RemoveMonthFromUserIssueMonth: migrating ==================================
-- remove_column(:user_issue_months, :month)
rake aborted!
An error has occurred, all later migrations canceled:

Mysql::Error: Table 'redmine.user_issue_months' doesn't exist: ALTER TABLE 
`user_issue_months` DROP `month`

(See full trace by running task with --trace)

Maybe just giving me the full  user_issue_months CREATE TABLE could be enought.

Thanks.

Original issue reported on code.google.com by joel.ale...@gmail.com on 15 Sep 2011 at 8:37

GoogleCodeExporter commented 9 years ago
Maybe this error occured in
redmine_work_time/db/migrate/008_remove_month_from_user_issue_month.rb

table:user_issue_months is created in
redmine_work_time/db/migrate/001_create_user_issue_months.rb .
And, initial columns are descrived in 001_create_user_issue_months.rb

If the column:month is already removed, 
you can register the [migrate flag]:'8-redmine_work_time' 
in table:'schema_migrations',
to skip this migration step(008).

Original comment by T.Kusukawa on 18 Sep 2011 at 3:18

GoogleCodeExporter commented 9 years ago
It seems that the db migration starts on step 8.

How can i force the migration to starts on step 1?

Original comment by joel.ale...@gmail.com on 19 Sep 2011 at 10:05

GoogleCodeExporter commented 9 years ago
i removed some old work_time entries that where on schema_migrations and it 
fixed it.

thanks.

Original comment by joel.ale...@gmail.com on 19 Sep 2011 at 10:47

GoogleCodeExporter commented 9 years ago
that's good.
thanks for your solution report.

Original comment by T.Kusukawa on 19 Sep 2011 at 1:36