The site creation is an important step, but its management will be as important in the future. It will be important to make mandatory steps like getting to the website migration. It goes without saying that the use of effective tool when these approach will be required. One of the most used in this context is ruby on rails and benefits greatly facilitate development work. In the case of migration, it is enough to know what to do with ruby on rails in order to be assured of the outcome.
The website migration
A ruby on rails developer can easily make migration with Active Record functionality of the framework. Clearly, migration essentially allow to change the schema of the database with time. The usual approach is therefore based on the writing of these changes in pure SQL. With migration, the use of a DSL ruby will be possible which will greatly facilitate the description of changes in the tables. therefore it will be seen each of these migration as new versions at the database. The scheme will therefore start as naked and migration will incorporate updates either at the tables, columns or entries. Active Record will know exactly how to update these data and will also update db / schema.rbfichier to have a perfect structure.
How to do?
You should know that migration is stored in the form of files regardless of the migration class. The file name is a UTC time stamp that identifies the migration followed by an underscore followed by the name of the migration issue. The last part of the file name must also be consistent with the name of the migration class. Admittedly, ruby on rails uses this timestamp to best manage the processing of migration and the order of this treatment. If so copy migration, or if it creates one, it will inevitably take its position into account. Of course, with Active record, a generator will come to calculate time stamps.
