Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrations to sql #5

Open
shoebox639 opened this issue Oct 7, 2010 · 0 comments
Open

Migrations to sql #5

shoebox639 opened this issue Oct 7, 2010 · 0 comments

Comments

@shoebox639
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant