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
I have a new Rails 4.2.1 app, followed usual Readme setup with Gemfile and placed "include ActiveUUID::UUID" line in my model. However, every time I run specs or rails console, the activeuuid patches have not been applied.
I added a break to the .apply method in ActiveUUID::Patches, and the mysql2 adapter,
ActiveRecord::ConnectionAdapters::Mysql2Adapter
is not defined at that point.
The result, if I start a console, is that I need to do a manual "ActiveUUID::Patches.apply!" to get things working.
Anybody else see this? Am I doing something wrong?
Odd part is, I have a Rails 4.2.0 app using activeuuid and all is good.
The text was updated successfully, but these errors were encountered:
I am seeing the exact same problem with a Rails 4.2.1 application in development environment.
I have added a migration to add a uuid column, and the migration fails because the previous run of ActiveUUID::Patches.apply! did not patch the respective classes, due to ActiveRecord::ConnectionAdapters::Mysql2Adapter not being defined.
For what it's worth:
Adding a simple ActiveRecord::Base, to initiate ActiveRecord class loading, before this line solves the issue for me in Rails 4.2.1.
I have a new Rails 4.2.1 app, followed usual Readme setup with Gemfile and placed "include ActiveUUID::UUID" line in my model. However, every time I run specs or rails console, the activeuuid patches have not been applied.
I added a break to the .apply method in ActiveUUID::Patches, and the mysql2 adapter,
ActiveRecord::ConnectionAdapters::Mysql2Adapter
is not defined at that point.
The result, if I start a console, is that I need to do a manual "ActiveUUID::Patches.apply!" to get things working.
Anybody else see this? Am I doing something wrong?
Odd part is, I have a Rails 4.2.0 app using activeuuid and all is good.
The text was updated successfully, but these errors were encountered: