Schema rb not updating
we do this are often glossed over by long-time Rails developers who know the history of the feature, leaving newcomers frustrated by a habit that seems confusing or redundant.To understand the Rails database management plan, you’ll need to keep in mind the needs of two different kinds of people who will be consuming your database changes: those with an existing environment and those setting up a new environment.
All these have something in common: they are already using your application with an existing database.It is just as easy to write the inital migration as an initial schema. However, if you do want to do that then you can use rake db:create to create the db from the schema.Note that this is not the question you asked originally, which was how to update the db from an updated schema.Make sure to only run this if you're not sharing gems with another application.If you're using RVM or another Ruby version manager, and switched to another Ruby version during the update, you can drop the old Ruby version.This method is faster, cleaner, and avoids all the ugly failures that can crop up in an extensive migration chain.
What seems like two different solutions is actually two parts of the same solution.
It might be you, a month from now, when you’ve massively screwed up your existing database and want to drop it and start fresh.
Be certain of one thing: sooner or later, a new environment come along, even if one doesn’t exist right this moment.
In order to put back to what it should be before running the migrations you can do rake db:schema:dump You can alternatively just revert using your Version Control System.
If you are not using a VCS then start doing so immediately, you will not regret it. I assume you are just getting started with Rails so have a look at all the Rails Guides and work through some tutorials.
Just creating a schema file for initializing the database at first.