-
Notifications
You must be signed in to change notification settings - Fork 484
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
Fix MySqlAdapter superclass bug via class_eval loading of superclasses #209
Conversation
FYI: You'll need to regenerate the
(History.txt should be |
Fix MySqlAdapter superclass bug via class_eval loading of superclasses
Thanks, I've merged this in and fixed the gemspec problem you pointed out. @etagwerker, would you mind pointing your Gemfile to |
@bmabey I wish I could say it all works alright pointing to master, but it doesn't. I get this stack trace if I try:
There is obviously some mixup, as it's looking for postgres info in a My application uses In that test, I am not testing the Rails engine, just my application. Any ideas? |
@bmabey Not fixed at all. Try to run test for https://github.com/svenfuchs/globalize3/tree/rails4 (rails4 branch).
Switch to |
Yup this is because of the superclass overwrite. We can fix this quickly by adding the postgres subclass monkey patch again, but the real fix is the proper decoration of the connection adapters. I started but I'm not familiar with the ARJDBC workaround decisions. |
@tommeier can you provide fast hack fix (maybe only in some branch)? I can help with proper fix, but I don't know database_cleaner codebase well. I spent yesterday one hour looking into it. This bug is triggered in features, not in specs. |
Hi @simi, there seems to be a lot of edge cases in this Could you please try with:
|
To get it working with my current setup (a lot of gem dependencies) and Rails 3.2.13.
Removing the
superclass mismatch for class MysqlAdapter
byclass_eval
as opposed to monkey patching the superclass.It was still erroring for me with the fix in #185. Would be great if @etagwerker (or others where this is an issue) could check if this fix also works for them.