-
Notifications
You must be signed in to change notification settings - Fork 111
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
Error with phony_normalize on migration #19
Comments
The Feel free to create a pull request :) |
Raise only an exception at validation for non-existing attributes (#19)
Hello, Thanks for the great tool! #phony_normalize with :as throws "not an attribute" exception when I attempt to create database column. Upon
Makes sense, in a way, since the database column's not yet been created. However, this does mean I can only run those commands by commenting out #phony_normalize. Am I doing everything correctly? Thanks Again, |
Quick thought- would it help to manually declare |
...it seems to work, at least. |
@JamesCropcho it does indeed. Migrations with conflicting models is an issue that happens more often. We could remove or maybe postpone the check however. Pull request welcome for this :) |
@joost I had success with manually declaring as an Regarding modification of current behavior- well, I actually like the sanity check you've put in, as is, myself. so I'm loathe to suggest modifying it, now that we have a workaround. Thanks again for the great tool, sir. -J |
Hello,
Every time I run a migration concerning a model with a
phony_normalize
, the following exception is raised :The exception is raised from
lib/phony_rails.rb:73
.A warning wouldn't be enough ? I have to comment every
phony_normalize
in my models before running a migration, then uncommenting them.The text was updated successfully, but these errors were encountered: