-
Notifications
You must be signed in to change notification settings - Fork 5
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
Apparently Rails 3.2 recursively looks into db/migrate folder #8
Comments
Is this resolved? |
Unfortunately, no. The main project I use this on is still Rails 3.0.x, so I haven't had the need to fix this just yet. I don't think the fix is hard, just moving where the migrations folder gets created (probably outside of db/migrations). Any help would be greatly appreciated! On Jan 22, 2013, at 6:12 PM, riddhima [email protected] wrote:
|
Well i am getting |
That's a good question. I would suspect they are not related. I've not tried to use SecondBase with rails 3.2 yet, so I'm honestly unaware of what issues there may be at this time. I will be using this in a 3.2 project in the future, so I will address the issues. Just not sure how soon. On Jan 22, 2013, at 7:35 PM, riddhima [email protected] wrote:
|
rake aborted! (See full trace by running task with --trace) Getting error on rake db:migrate |
so it wants to make SecondDB migrations in main DB
The text was updated successfully, but these errors were encountered: