[Solved] How do I access user’s field in show page? [closed]

Question

Welcome to the Rails world! First thing to mention is that Ruby is a language, and Rails is a framework that uses Ruby language. Migrations are a part of Rails and are not a part of Ruby.

Now to your question about migrations. Yes, each table needs migrations for its creation and later migrations for each table adjustment/change, if required (unless you want to do all your table modifications through pure SQL, which you DON’T).

And another part of your question about databases. In a simple case Rails is designed to have 3 databases for 3 different purposes – development, testing, and production. You use the same migrations for all of them. First, you apply your migrations to your local development database and do your code implementation. In parallel, you write tests and also apply the same migrations to your testing database. And when you are done, you deploy everything to your production server and apply your migrations to production database.

I guess it is a general workflow with migrations. As for details, you should really go over migrations manual or even better to start with “Getting Started” section.

Accepted Answer

Welcome to the Rails world! First thing to mention is that Ruby is a language, and Rails is a framework that uses Ruby language. Migrations are a part of Rails and are not a part of Ruby.

Now to your question about migrations. Yes, each table needs migrations for its creation and later migrations for each table adjustment/change, if required (unless you want to do all your table modifications through pure SQL, which you DON’T).

And another part of your question about databases. In a simple case Rails is designed to have 3 databases for 3 different purposes – development, testing, and production. You use the same migrations for all of them. First, you apply your migrations to your local development database and do your code implementation. In parallel, you write tests and also apply the same migrations to your testing database. And when you are done, you deploy everything to your production server and apply your migrations to production database.

I guess it is a general workflow with migrations. As for details, you should really go over migrations manual or even better to start with “Getting Started” section.