Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I plan on using a “base script” for my initial database version 1.0.0 but after that I will require change scripts which “upgrade” the database to newer versions. I’m not sure how to name these scripts in my repository.
I was envisioning something along the lines of:
What is a good naming convention to use and why?
Rails uses timestamped migration files. Each file starts off with a database-style timestamp followed by a short description:
20080717013526_your_migration_name.rb. This ensures they show up in order and give you information about what the migration actually does. It’s just one approach, but I think it works well.