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

Handle ActiveRecord::NoDatabaseError exception #323

Conversation

chopraanmol1
Copy link
Contributor

Fixes #322

Related Information

rails/rails#32870 (comment)

@chopraanmol1 chopraanmol1 force-pushed the handle_no_database_error_exception branch from 417cd24 to e0bfe5f Compare August 30, 2018 06:25
@chopraanmol1
Copy link
Contributor Author

The current behavior, when the table doesn't exist, is to skip serialization. To keep things consistent I've skipped serialization for the scenario when a database doesn't exist. I've also added a warning message when the above scenarios happen.

But I think it can be argued that default behavior for the above two scenarios should be to serialize without checking for column type instead of skipping serialization(as we cannot check column type).

I think the default behavior should be discussed and if a change is required, I'll modify this PR or create another PR whichever is more appropriate.

@skunkworker
Copy link

This fixes my error upon database create.

@pokonski
Copy link
Member

Fantastic! Thanks for the fix @chopraanmol1!

@pokonski pokonski merged commit 3e6cbf6 into public-activity:1-6-stable Aug 31, 2018
@pokonski
Copy link
Member

Fix released in 1.6.2!

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

Successfully merging this pull request may close these issues.

None yet

3 participants