You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all the database migrations are done with rails migration framework. That works for very simple applications. As the app gets more complex with more tables and more complex relationships, this migration scheme just doesn't work very well. For example, it doesn't let you do compound primary keys, foreign keys, certain constraints and stuff like that.
Ruby does support just putting sql in those migration files. I think the best way to go about it is to set up a migration path to only use actual SQL in our migrations. Another option is to still go with the rails migrations because it does support a lot of different databases and we don't have to write different sql if we decide to change db's.
The text was updated successfully, but these errors were encountered:
Currently all the database migrations are done with rails migration framework. That works for very simple applications. As the app gets more complex with more tables and more complex relationships, this migration scheme just doesn't work very well. For example, it doesn't let you do compound primary keys, foreign keys, certain constraints and stuff like that.
Ruby does support just putting sql in those migration files. I think the best way to go about it is to set up a migration path to only use actual SQL in our migrations. Another option is to still go with the rails migrations because it does support a lot of different databases and we don't have to write different sql if we decide to change db's.
The text was updated successfully, but these errors were encountered: