Migrations will not run on a fresh database
Reported by Ian White | April 14th, 2008 @ 12:33 PM
When migrating to a specified version on a clean db, the schema_migrations table can't be found, and an error is raised.
On a clean rails app:
script/generate migration Foo
create db/migrate
create db/migrate/20080414172731_foo.rb
rake db:migrate VERSION=20080414172731
rake aborted!
SQLite3::SQLException: no such table: schema_migrations: SELECT version FROM schema_migrations
Comments and changes to this ticket
-
Ian White April 14th, 2008 @ 12:40 PM
Here's a git patch that adds a test for the above ticket, and fixes it
-
Ian White April 14th, 2008 @ 01:08 PM
The fix is here:
-
-
Sam Granieri April 14th, 2008 @ 05:08 PM
+1
Nice catch Ian, but the workflow you describe in getting to the problem is something i've never experienced
-
Ian White April 15th, 2008 @ 04:15 AM
If your test/ci stuff wipes out a database then migrates up to a particular version, then you'll see this.
The reason I saw is that this is exactly what rspec does. See http://rspec.lighthouseapp.com/p...
-
Ian White April 15th, 2008 @ 09:57 AM
The commit url http://github.com/ianwhite/rails...
(still learning github)
-
Joshua Peek April 17th, 2008 @ 01:33 PM
- → State changed from “new” to “open”
- → Title changed from “Since r9244, migrations broken on clean db” to “Migrations will not run on a fresh database”
- → Assigned user changed from “” to “Joshua Peek”
-
Repository April 17th, 2008 @ 01:44 PM
- → State changed from “open” to “resolved”
(from [82b4faf81218bbd8916ab559590db236c7f80e46]) Fix migrations when migrating to a specified version number with a fresh database [#1 state:resolved]
Signed-off-by: Joshua Peek
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
