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
Globalize breaks rake db:create using Rails 4.2 #384
Comments
@mparramont I've just hit a similar (the same?) error. I assume the backtrace references the call to |
Not yet, now that Rails 4.2 is officially out I guess the globalize people will take a look at it 😄 |
The actual released 4.2 doesn't have this problem. I can happily run rake db:create without a problem. However I do get tons of deprecation warnings about support for serialized attributes due to be removed in R5. See paper-trail-gem/paper_trail#416 in PaperTrail. I'll raise the same issue here. |
i have similar problem on my local, too.
when i run
|
The https://github.com/spree-contrib/spree_i18n project is broken on Rails 4.2 w/Globalize 5.0.0 with similar error. Anytime we try to build the test app I hit an error that database table doesn't exist coming from the first models
Relevant decorator:
|
Actually I think my error may be related to #406 just tried out running globalize form source and it fixed my issue so looks like just waiting on v5.0.1 |
I would try this out again on 5.0.1 guys my error cleared up with it's release. |
@JDutil so 5.0.1 solved this issue? |
Well it resolved the error I was having which was very similar, but mine said the table didn't exist not that the column didn't exist. Not sure that makes a difference or not, but both errors start soon as the code tried to evaluate the |
Thanks for info. That's the same error AFAIK. One is just from PG and second from MySQL (or sqlite). I'm happy to close this. |
Result from
rake db:create
with Rails 4.2.0.beta4:Result from
rake db:create
with Rails 4.1.7:Relevant model code from
campaign.rb
The text was updated successfully, but these errors were encountered: