This project is archived and is in readonly mode.
Clarifying rake:db:migrate & dump
Reported by Trevor Turk | November 12th, 2008 @ 09:38 PM | in 2.x
I was confused as to why certain database tables were mysteriously reappearing in my db/schema.rb file, even though I (thought) I'd removed them a long time ago.
Here's what I think is happening:
1) I run rake db:migrate 2) this invokes the db:schema:dump task 3) this adds any tables/columns that exist in the actual database schema to db/schema.rb
I'm not sure if this is the case, but I wanted to file a ticket in the hopes that someone could confirm and document this. I'm attaching a documentation patch in the hopes that I'm understanding what's going on correctly.
Thanks!
Comments and changes to this ticket
-
Trevor Turk November 15th, 2008 @ 06:55 PM
- Assigned user cleared.
This has been committed to docrails:
http://github.com/lifo/docrails/...
I don't think I'm able to close this ticket, though.
-
Pratik November 15th, 2008 @ 07:17 PM
- State changed from “new” to “resolved”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Pratik
Trevor Turk