Home/ Questions/Q 6738809
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T11:24:45+00:00

I have created a database with devise and the nifty generator. I’m trying to

  • 0

I have created a database with devise and the nifty generator. I’m trying to make a new database with the nifty generator (rails g nifty:scaffold Asset user_id:integer), but when I try to migrate the database (rake db:migrate), I get the following error:

charlotte-dator:showwwdown holgersindbaek$ rake db:migrate
==  DeviseCreateUsers: migrating ==============================================
-- create_table(:users)
rake aborted!
An error has occurred, all later migrations canceled:

Mysql2::Error: Table 'users' already exists: CREATE TABLE `users` (`id` int(11) DEFAULT NULL auto_increment PRIMARY KEY, `email` varchar(255) DEFAULT '' NOT NULL, `encrypted_password` varchar(128) DEFAULT '' NOT NULL, `reset_password_token` varchar(255), `reset_password_sent_at` datetime, `remember_created_at` datetime, `sign_in_count` int(11) DEFAULT 0, `current_sign_in_at` datetime, `last_sign_in_at` datetime, `current_sign_in_ip` varchar(255), `last_sign_in_ip` varchar(255), `name` varchar(255), `created_at` datetime, `updated_at` datetime) ENGINE=InnoDB

Tasks: TOP => db:migrate
(See full trace by running task with --trace)

I’m following a tutorial and have quite a hard time understanding why this happens. Can anyone explain what is going on?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The migration is trying to create a table that already exists in your database.

    Try to remove the user table from your database. Something went wrong with you migration process. You should also compare your schema.rb version with your db/migrate/*.rb files.

    Clarification:

    It seems that many SO users don’t agree with my reply, either because they consider it inaccurate or not recommended.

    Removing a table is always destructive, and I think that everyone understands that.

    I should have mentioned add_column, since the table was being created in another migration file.

    • 0